News for hackers. Stuff that matters.
Re:The cost of transpiling ES2015 in 2016 by thealphanerd on Monday February 08, 2016 @11:32AM (#11059039)
Careful checking in you build folder. If there are any native modules, and you are not on the same architecture, everything will explode.

This can be avoided by adding "npm rebuild" to your deployment.

Re:The cost of transpiling ES2015 in 2016 by tjelen on Monday February 08, 2016 @11:46AM (#11059154)
I guess you mean the node_modules folder, where in fact this makes a lot of sense. What OP means is the build folder to which the frontend part of project is compiled.
Re:The cost of transpiling ES2015 in 2016 by true_religion on Monday February 08, 2016 @08:19PM (#11062340)
I've been contemplating just checking in the build folder.

It does feel like a code smell, but it'd make deployment easier.

Our frontend is Javascript, wherein there's no worry about native modules.

Our backend is Python running Pypy, so there's no native code there either.