Skip to content
Steve Lee edited this page Feb 7, 2016 · 4 revisions

There are many, many technology choices available and new frameworks appear each day. Although an opinionated framework means less decision to be made, it also increase the barriers to collaboration. Given our principles we prefer small libraries so that even if they become unsupported we can still use them

Technologies

  • git and GitHub
  • node.js 4.x.x LTS build and server runtime
  • npm 2.x.x build and package management
  • Browserify Bundling and require on client plus hot reload
  • Hapi - http server. More complex than express but batteries included and configuration based.
  • RxJS observables and streams for async
  • cyclejs client architecture and possibly server
  • Senecajs for packages / services
  • Database TBD - might be rethink

Workflow

  • npm scripts and possibly make
  • Tape for Unit Testing
  • Integration test TBD
  • CI / CD TBD

Dev on windows:

  • VisualStudio 2015 Community with nodejstools and/or VS Code IDEs as add minimal dependencies
  • GitHub for windows for GUI
  • Git for Windows for Bash shell on command line
  • ConEmu for terminal emulation
  • portable npm scripts - but can assume bash executables like rm
Clone this wiki locally