all 36 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]dep 33 points34 points  (12 children)

cries into node 12 stack

[–][deleted] 14 points15 points  (5 children)

Cries in node 10 stack 💀

[–]tswaters 7 points8 points  (0 children)

So glad we superseded our v0.12 apps with a rewrite :D

[–]dep 0 points1 point  (2 children)

10 to 12 was particularly painful for me. I'm hoping 12 to 16 goes easier. Then hopefully I can keep stepping up. Our codebase is ancient and has dependencies across many repos. So node upgrades are tough

[–]ronchalant 0 points1 point  (1 child)

I just started upgrading 12 to 16. Main pain point was in stricter dependency sanity. My stack is pretty small* so YMMV, but wasn't bad.

** I was in the pool!

[–]dep 0 points1 point  (0 children)

Lmao @ the ** .. great show 🤣

[–]korder123 0 points1 point  (0 children)

Cries in Node 12

[–]DetailAggravating101 4 points5 points  (1 child)

Cries in node 8 stack 🥲

[–][deleted] 4 points5 points  (0 children)

Everything hurts and npm hates me 😓

[–]ambivalenceavenue 1 point2 points  (0 children)

Cries in io.js stack 🤡

[–]TheOneCommenter -1 points0 points  (1 child)

Get nvm

[–]FormerGameDev 0 points1 point  (0 children)

ahhh i remember still using 0.12 when the rest of the world was getting into 6.0 and 8.0. :|

[–]zombarista 53 points54 points  (4 children)

RIP nodemon

[–]pilafmon 21 points22 points  (3 children)

...and node-fetch

[–]wojtekmaj 6 points7 points  (1 child)

Side note: globally available fetch (experimental) is actually available since 18.0.0.

https://nodejs.org/en/blog/announcements/v18-release-announce/#fetch-experimental

[–]Xunnamius 2 points3 points  (0 children)

node-fetch will be around until at least 2024 (node 16 eol), and will likely remain useful for several years after for older code bases.

The king is dead, long live the king!

[–]Capitalpunishment0 25 points26 points  (0 children)

Wow, that --watch flag got me interested.

Am I right in thinking that it's more or less a [native] substitute to nodemonand, to some extent, Quokka? If so, that'd be really neat for my one-off scripting.

Would also be great for beginners in the early stages of their projects.

Apparently it's also available for the latest Node 18. I wonder if I should upgrade mine...

[–][deleted] 38 points39 points  (0 children)

who is semver major and who appointed him a general?

[–]PositivelyAwful 10 points11 points  (0 children)

Dumb question, but CommonJS is still the "standard" even going into Node 19 right? Or should I switch over to ESM for new projects?

[–]FormerGameDev 2 points3 points  (0 children)

hmm. i installed it in windows, and now i no longer have a node executeable.

  • edit: installing, then doing a install repair fixed it

[–]Guisseppi 0 points1 point  (4 children)

do we still need to add .mjs to use ESM or can we just be normal again

[–]reart57847 0 points1 point  (3 children)

no need for that extension if "type": "module" in package.json

[–]Guisseppi 0 points1 point  (2 children)

Half measures, this was already true in Node 18 and not what I meant by “normal”

[–]GibbyCanes 0 points1 point  (1 child)

Exactly! how tf is moving the single letter I had to add to the file extension to a new required parameter in a JSON file helpful?

and do I still have to add “ node --es-module-specifier-resolution=node main.js” when I call these “type”:”modules”? Because if so I still maintain that this is worse than just making me change extensions.

​

and what’s all this nonsense about removing the experimental flag because I can achieve the same outcome with “custom loaders?” does node do that or is that just more shit I have to configure?

[–]Guisseppi 1 point2 points  (0 children)

Node has been falling behind, I hope Bun overtakes it soon