Use flags with command line tools to record dependencies in tracked files:
package.json(npm)bower.json(bower)
Installed files should be ignored unless there is good reason to track:
node_modules(npm)bower_components(bower)
And with bower, we like moving files where needed rather than exposing everything in the public directory.
We like automating things, like build steps, testing, deployment, etc.
We like to compile resources down to a minimal number of minified files for the browser.
We like using Gulp.js for build tasks.
- AVOID GLOBALS AS MUCH AS HUMANLY POSSIBLE.
- CommonJS: break things into small, reusable, single-purpose modules. Avoid globals.
- React.js: encapsulate complex logic in many small, reusable, single-purpose components.
- Webpack: bundle all our small modules and components up into a few optimized files for the browser.
- APIS + Client Side Applications = Happy Developers
- jshint: automatically check code formatting.
- editorconfig: shared editor configurations across the team to make it easy to adhere to coding standards when they differ per technology.
There's a lot of good stuff here that I would adopt:
https://github.com/rwaldron/idiomatic.js#idiomatic-style-manifesto
- semver
- Code reviews