yoshuawuyts / modules Goto Github PK

• what is a generator?
• yield
• yield*
• build your own co
• yielding arrays
• yielding promises
• async.sequence esque stuff
• fibonnacci

one patch may call multiple endpoints, which might have varying permissions. Build a thingy (possibly just a co example) that resolves all of 'em.

general listener that reacts to these and then calls your favorite logger to log something.

need a small tool to bind multiple callbacks to a single event. Much simpler in scope than barracks

not a real standard, but hey we can try

bin              -> executables
docs             -> documentation
pkg              -> packages (local modules)
sh               -> shell scripts
lib              -> source files
test             -> tests

• curie parser
• zoom level expander
• faxify that shit

all the slack bots running in docker containers talking through nginx. ANARCHY AND LOUDBOT

https://api.slack.com/community
https://github.com/swirlycheetah/slack-brewbow

Calling all files index.js makes atom sad. Instead prepend the parent dirname so we can get more context.

yellow line @150 lines
red line @300 lines

https://github.com/travis-ci/travis-web-log/blob/master/lib/log/deansi.coffee

logging escaper. cuz, man we need that badly.

http://williamdurand.fr/2014/02/14/please-do-not-patch-like-an-idiot/
https://github.com/bruth/jsonpatch-js

simply update a value, and create the whole shebang to be processed. Should make spec-compliant requests a helluva lot easier.

• autoprefixing
• cleaning up of repo

cause the styles are mad ugly

• update brewfile
• update caskfile
• find a way to work with stow

similar to jscmd, expose css <command>.
Probably want to wrap csslint and rework until sheetify is ready. Might have to do some messing around with the rework mapping to make it adhere to the browserify way™.

• logging
• response time
• body parsing

build the files and serve 'em to the client. Autoreload = just killing the damn server.

add a way of cascading permissions, possibly dependent on env variables.

user
admin (+user)
owner (+user +admin)

https://github.com/kevva/squeak
https://github.com/koajs/accesslog

https://github.com/tj/make-lint but for jsfmt

writing md files is easy, displaying them nicely is hard. Start off by parsing a docs dir and concatting all the stuff there into something nice.

scan a dir recursively for files and register files as gulp tasks. Kinda turns your gulpfile into a one-liner.

Build an api based on a dir layout

api/
  users/
    settings/
      get.js
    get.js
    patch.js
  index.js

• regex-email
• regex-iso-date