My belief is that Node.js is backwards patible. A script that runs in Node.js N should also run in Node.js N+1. Is there any documentation that I couldn't find mentioning this? Or is there some way of knowing other than simply installing a newer version and test it?

I've written some scripts a few years ago, back when the current Node.js major release was v5. I want to upgrade the system, but need to be sure that the current process will not break.

My belief is that Node.js is backwards patible. A script that runs in Node.js N should also run in Node.js N+1. Is there any documentation that I couldn't find mentioning this? Or is there some way of knowing other than simply installing a newer version and test it?

I've written some scripts a few years ago, back when the current Node.js major release was v5. I want to upgrade the system, but need to be sure that the current process will not break.

• javascript
• node.js

• 5 Javascript will probably always be backwards patible, since they won't break anything on the web. Node-specific APIs may someday change. There's no such thing as "forward patibility", only backwards patible interpreters and APIs. – deceze ♦ Commented Nov 15, 2019 at 14:27
• @deceze There are ways of designing an API/protocol so that it is impossible to extend it while preserving backwards-patibility. Those would be called "not forward-patible". – Bergi Commented Nov 15, 2019 at 14:40
• 3 "Forward patible" would mean "Is today's Node.js patible with future versions and features of Javascript?", and the answer would necessarily be no. – Jeremy Thille Commented Nov 15, 2019 at 14:40
• Node major releases have definitely deprecated and removed functions and modules (or methods within modules). The ABI has changed significantly several times (in earlier versions especially) as well. – Joe Commented Nov 15, 2019 at 15:50

1 Answer 1

I guess that what you are looking for is this website.