You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
v6 has been in beta since Nov 4, 2019 (nearly 4 years) and it appears that v5 is not being maintained for current versions of node (fails on v20 requiring C tools and such to build from source).
Also, v6 is the default install when running npm install --save zeromq
If production deploys are supposed to be using v6, that's not beta.
Since v6 is being actively maintained for current node releases and v5 is not, why not drop the scary banner, go full-on v6.18.0.
... unless v6 is still subject to breaking changes.
If v6 is still subject to breaking changes, it shouldn't be the default install.
Uh oh!
There was an error while loading. Please reload this page.
v6 has been in beta since
Nov 4, 2019(nearly 4 years) and it appears that v5 is not being maintained for current versions of node (fails on v20 requiring C tools and such to build from source).Also, v6 is the default install when running
npm install --save zeromqIf production deploys are supposed to be using v6, that's not beta.
Since v6 is being actively maintained for current node releases and v5 is not, why not drop the scary banner, go full-on v6.18.0.
... unless v6 is still subject to breaking changes.
If v6 is still subject to breaking changes, it shouldn't be the default install.
If it isn't, just bump it and go! 🚀
Re: #529
The text was updated successfully, but these errors were encountered: