5
1
u/Skaft Apr 27 '16
Do you guys upgrade instantly when a new version is out? Do you need to change anything in your projects to make it work?
3
u/Bieb Apr 27 '16 edited Apr 27 '16
It really depends. If you really want to be safe, you should be writing unit tests and even integration tests if your project is complex enough. Otherwise it's just a matter of waiting and seeing if anything breaks as you really cannot know 100%.
It's also helpful to look through the breaking changes in the change log.
One of the big things for some of my published npm modules and other code is the changes to Buffer. Using "new Buffer()" is now deprecated in favor of Buffer.from(), Buffer.alloc(), etc. The constructors weren't removed, but I imagine in the future they will be, maybe version 7+.
1
u/THIS_BOT Apr 27 '16
on personal projects that I do for fun, I try to track the latest and greatest, but for things that I plan on maintaining, I stick to LTS (so Node >=v4.2). Too much changes on the non-LTS path to justify spending time keeping everything compatible.
2
u/sanosukesagara Apr 27 '16
From the schedule, v6 should be LTS. Can somebody enlightened me whether is this LTS? I am planning for a project for production soon.
1
1
u/gergelyke Apr 27 '16
If you are interested in a more tech-focused overview, check this out: https://blog.risingstack.com/whats-new-in-node-v6/
0
8
u/joshmanders Apr 26 '16
If you use Node in Docker, I have released v6.0.0 images that support node-gyp dependencies.
https://hub.docker.com/r/stackci/node/tags/