stringparser

grep -oh 'url[^)]*' ./**/*.css | grep -o "[/.][^\\'\\\"?#]*"

stringparser

alias grune='git branch --merged | egrep -v "(^\*|master|dev)" | xargs git branch -d'
alias drune='docker rm $(docker ps -aq)'

stringparser

Documentation

Ideas about documenting enough for non-library projects.

Motivation

The aim of this document is to give rules to follow in order to make a project understandable from a producer and consumer point of view. The idea is to have a simple setup where code self-documents itself whenever possible. When this is not possible we will give options on how to go about it.

Where to start?

stringparser

;[Element].forEach(function(self){

  self.prototype.eventListenerList = {};
  self.prototype._addEventListener = self.prototype.addEventListener;
  self.prototype.addEventListener = function(type, handle, useCapture) {
    
    useCapture = useCapture === void 0 ? false : useCapture;
    var node = this;

    node._addEventListener(type, handle, useCapture);

stringparser

# boostrap nested npm modules installation
npm-boot() {
  local INIT_DIR=$PWD

  # go through all packages and install their dependencies
  for package in `ls ./**/package.json | grep -v node_modules`
    do
      cd $INIT_DIR
      cd $(dirname $package)
      echo "Installing modules for $PWD"

stringparser

react, typescript, redux, webpack

Bootstrapped with Create React App Typescript and customized.

stack and setup

• Typescript to add types to JavaScript
• Webpack to build the application
• React for the views
• redux for application state management

stringparser

Inspired on this other gist

function hook(callback){
  
  var oldWrite = process.stdout.write;
  var output = { str : '' };

  return {
    restore : function(){