NodeSource Blog
nodesource.com · Company blog · on HN since 2014
NodeSource, a Node.js tooling company, writes about Node releases, npm usage, long-term support, and enterprise Node.
What HN saysHN commenters cite it as a reference for Node.js release lines and LTS support timelines, plus a post on Guy Fieri in npm packages.
58HN people shared it
16linked it in comments
75stories submitted
958story points
1 year agolast shared
2014people per year2026
Most-shared posts
- 111 Simple Npm Tricks That Will Knock Your Wombat Socks Off4 people · 11 points · first shared 2016 · discussion on HN
- 2Essential Steps: Long Term Support for Node.js4 people · 1 points · first shared 2015 · discussion on HN
- 3The State of Desktop Applications in Node.js3 people · 139 points · first shared 2014 · 113 comments on HN
- 4Understanding the Node.js Event Loop3 people · 137 points · first shared 2015 · 23 comments on HN
- 5Is Guy Fieri in Your Node.js Packages? (2016)3 people · 29 points · first shared 2016 · 4 comments on HN
- 6Announcing a Node.js Snap for Linux3 people · 5 points · first shared 2018 · discussion on HN
- 7Node by the Numbers 20163 people · 2 points · first shared 2017 · discussion on HN
- 8N|Solid. Enterprise Node. Finally3 people · 2 points · first shared 2015 · discussion on HN
- 9Certified modules3 people · first shared 2017
- 1015 Essential Packages to Get Started with Electron2 people · 16 points · first shared 2016 · 1 comments on HN
- 11Installing Node.js tutorial2 people · 9 points · first shared 2018 · 1 comments on HN
- 12Security Tips to Keep Express from Getting Pwned2 people · 5 points · first shared 2016 · discussion on HN
- 13The Age of “Node.js and…”2 people · 3 points · first shared 2018 · discussion on HN
- 14Understanding how node js release lines work2 people · first shared 2018
- 15Why the New V8 Is So Damn Fast1 people · 338 points · first shared 2018 · 233 comments on HN
What HN people wrote when they linked it
blacksmith_tb · 2016-04-26
It might be worth trying to get to 4.2.0, which was the first LTS [1] release (due to the change in versioning, that's only six months older than 4.2.0).
1: https://nodesource.com/blog/essential-steps-long-term-support-for-node…
chrisfosterelli · 2016-03-23
The caret character is a specification in NPM, not semver. It's designed to work within the semantic versioning rules to ensure you get the latest version which includes bug fixes, but also won't include breaking changes.
For example, ^1.3.2 will allow anything greater than 1.3.2 but not 2.0.0. It also has special behaviour that makes it more strict for projects with a major version of 0. If your dependencies follow semver then you'll get bug fixes and security updates without having to do anything or worry about breaking changes.
More info: https://nodesource.com/blog/semver-tilde-and-caret/
cratermoon · 2023-06-24
Not quite. Odd releases EOL with the next release. Even releases are on LTS. https://nodesource.com/blog/understanding-how-node-js-release-lines-wo…
rsj_hn · 2021-03-01
related: Guy Fieri in node
https://nodesource.com/blog/is-guy-fieri-in-your-node-js-packages/
the_duke · 2018-11-01
A LTS version is maintained for 36 months total.
(6 months regular release support, 18 months active LTS, 12 months maintenance LTS)
For details, see https://nodesource.com/blog/understanding-how-node-js-release-lines-wo…
piotrkubisa · 2018-10-24
10.x soon will get a LTS badge [1], so we can expect 10.x (not 11.x) will be added into 19.04 apt repository.
nvm is probably the easiest way to install it, but of course, you can do it manually:
1. mkdir -p ~/apps/
2. Download tar.gz and extract it to ~/apps/
3. Change $PATH variable to include the bin directory
NODEJS_DIR="node-v8.12.0-linux-x64" # Change version to appropriate
export PATH=$PATH:${HOME}/apps/${NODEJS_DIR}/bin
4. Validate "installation" by version check
[1]: https://github.com/nodejs/Release#release-schedule
Edit: There is also a snap package with nodejs - https://nodesource.com/blog/announcing-node-js-snap-linux-users/ but there is 12.x (edge channel) not 11.x
snap info node
greenleafjacob · 2018-07-13
I’ve not used it but https://nodesource.com/products/certified-modules
maxharris · 2017-08-05
TAForObvReasons · 2017-08-01
There are attempts like https://nodesource.com/products/certified-modules but do you trust the ratings if they don't have control over those modules?
caniszczyk · 2017-02-06
I think the NodeJS Foundation (https://nodejs.org/en/) and project are really successful and putting them under the auspices of the LF helped resolve a lot of community issues (including the io.js fork): https://nodesource.com/node-by-numbers
I'm not familiar enough with Express to comment on it.
alessioalex · 2016-10-25
Not unless you want a lot of people upset that their dependencies aren't installing: "Myles Borins (@thealphanerd) recently ran citgm with yarn, and shared the results. It was 25 minutes faster than npm, but 20 modules failed to install." ( https://nodesource.com/blog/the-definitive-guide-to-the-first-three-da… )
retrohack3r · 2016-08-17
N|Solid is free for development and can be downloaded from https://nodesource.com/products/nsolid
qntmfred · 2015-10-30
This release timeframe was announced quite a while ago. As others have mentioned the quick jump from 4 to 5 was primarily due to the io.js convergence.
Expect future major releases on a 6 month cadence with LTS releases every 12 months
https://nodesource.com/blog/essential-steps-long-term-support-for-node…
cpeterso · 2015-09-08
Here is a timeline diagram showing how the LTS and Stable branches will work:
https://nodesource.com/assets/blog/essential-steps-lts/nodejs_lts_sche…
From this NodeSource post:
https://nodesource.com/blog/essential-steps-long-term-support-for-node…
sova · 2015-07-04
Typically Node.js is for high I/O web applications. Thanks to the wonderful asynchronicity of javascript (callbacks "let me know when this is ready/done") it's really wonderful for browser-based programs.
However, there is growing discussion about using Node.js for desktop applications. Please see https://nodesource.com/blog/node-desktop-applications
blfr · 2015-04-22
This bothers me as well. Even tasks as simple as adding a repository are now being "improved" with a curl | sudo bash style setup[1].
However, installing from source with make was (and remains) a mess. It may work if you're dedicated to maintaining one application and (part of) its stack. But even then it usually leads to out of date software and tracking versions by hand.
Many people have this weird aversion to doing basic sysadmin stuff with Linux. What makes it weird is that it's really simple. Often easier than figuring out another deploy system.
(The neckbeard in me blames the popularity of OSX on dev machines.)
[1] https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-…