Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Current preferred setup is:

- npm for javascript dependencies

- vendor dir for sass deps (I've had problems with Bower don't run enough deps to put up with it)

- Webpack [1] and some shell scripts for builds. Webpack does all the hard/coordinated stuff and the scripts copy files. I've used Rake, Grunt, and Gulp with Browserify to do the same things and find my current setup works better.

[1] https://github.com/petehunt/webpack-howto

- Sass. I strongly dislike Less.

- React with Bacon

- Jest for testing. I'm not completely thrilled with this. It's awesome when it works but I've also spent half a day tracking down a bug that turned out to not be a bug and instead an artifact of the Jest module loader.

- Vim with my own set of javascript + library UltiSnips snippets. Tip: when you're writing library snippets, write them as e.g. 'react.snippets' and NOT 'javascript_react.snippets'. This prevents the various library snippets from interfering with each other. Vim supports a file having multiple simultaneous filetypes using a dotted notation `:set ft=javascript.react` and you can use ftdetect to automate the setting.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: