Has anyone tried running pubnub sdk in node 12.x?
On their docs, found that it supports till node 8. Link - https://www.pubnub.com/docs/web-javascript/supported-platforms
Does anyone have any updates whether they are going to add support for 12 soon or any possible workaround?
PubNub Node Versions Support
Thanks for bringing this to our attention. We are building in travis on node 12 with success, we just need to update the supported versions. We will likely update it when when do a new release (4.27.2) today.
Related
Would there ever be a case where we shouldn't use the latest stable version of node with the latest version Angular? Whenever I read the Angular update guide, there is always a mention of the minimum version of node to be used with that version Angular. So rather than worrying about using the minimum version of node, just use the current stable version.
Are there any drawbacks to doing that?
I'm not aware of anything that may create a problem here, so yes, but...
As this answer mentions it, you'll find in this link every node version that are safe to use with the version of angular you're using.
I am currently using node 6.1 in my project.
I want to upgrade it to latest stable version now.
Before doing that I want to know what are the breaking changes introduced in all the versions in between 6 to 12
Is there any place I can get all these breaking changes for the node versions.
I've found this page to be the most helpful list of all major/minor/patch changes:
https://nodejs.org/en/blog/release/v16.0.0/
Another good resource to find changes to all the different major versions, is the changelog archive on nodejs' github:
https://github.com/nodejs/node/tree/main/doc/changelogs
I haven't updated my Node for a very long time. My current version is v.6.12.3
Would there be any bugs if I don't update my Node?
Node 6 has long-term support state until April, 2019.
Node 6.12 is quite stable and has 99% support for ES6, it's acceptable to use it for development. It's recommended to update to latest Node 6 release for security and bug fixes, especially in production.
It's possible that some packages use features that aren't supported by Node 6 or mark it as unsupported in package.json engines, but in fact almost every third-party package still supports it.
Even in an extremely simple setting, I'm unable to get any breakpoints in my code to hit. See the attached screenshot. After hitting 'Debug "main.js"', the execution is never interrupted.
Since you are using Node v7.x ... the solution for now is:
either downgrade Node to v6.x
or WebStorm to older version.
From this official comment:
Are you using Node 7.x? It's a known issue unfortunately, see https://youtrack.jetbrains.com/issue/WEB-24629. Hidden option for turning dev tools protocol support off (js.debugger.node.use.inspect=false) will be included in next 2016.3 update - see https://youtrack.jetbrains.com/issue/WEB-24629#comment=27-1809582.
For now the only workaround is downgrading Node.js to 6.x :( Full Node 7 support (using v8 inspector) will be available in 2017.1
You may also try latest EAP build of 2017.1 -- https://confluence.jetbrains.com/display/WI/WebStorm+EAP -- it may have that fix already available (sorry, not using NodeJS myself so cannot confirm it).
Meteor is typically behind in Node.js version because it is a framework that uses its own bundled version of Node.js, and its APIs and features are built to rely on that version of Node.js.
I'm sure that in many cases upgrading Node.js poses no problem.
As an example, Meteor 2.10 at time of writing ships with Node.js 14. But we're already on Node.js 19.
Is there a way to tell Meteor (f.e. with the meteor cli, or some meteor package) to use newer versions of Node.js (and npm)?
Meteor 1.4 now supports Node 4.4.7!
See release notes
To upgrade to Meteor 1.4:
Go to the root of your project's directory
meteor update
Meteor does not support NodeJS 4+ as of now. The discussion is available in https://github.com/meteor/meteor/issues/5124
The latest update to the thread on April 29 is:
Guys, relax. The difference between Node version 4, 5 and 6 are relatively minor, and so if Meteor can support one, it can and will support all others. Ben created PRs for every currently active and supported Node version, but the fundamental part of the work is about making Meteor work with any (recent, non-legacy) Node version, and from there basically everyone should be able to freely select whichever one fits their goals and intentions best (i.e. 4.x if you don't care for bleeding edge Node, 6.x if you do; 5.x is not going to stick around for very long as it's not an LTS version).
So come and check out and help with the PRs if you're interested and
you can, but if not, just rest assured this is being worked on and
prioritized appropriately and I'm pretty sure Ben (and/or others
working on this) will keep everyone posted on any meaningful progress.