New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nodejs: merge with nodejs-lts #40106
Conversation
Hmm, I think we had the |
all in favor of updating node. I can't update |
3b5abe0
to
62e73e5
Compare
Can I rely on this PR for openssl3 update #37681 ? |
No, chronograf still doesn't build with nodejs 16, this will be merged when it does, but I have not been able to fix it so far. |
Have you tried updating it to 1.10.0 ? |
I did, but there was an error and since I don't know nodejs, I ended there. 1.10.0 should support nodejs 16 though |
@paper42 I was able to build it with
cc mantainer @the-maldridge |
@dkwo great, could you open a PR with that change? |
done #42644 |
@paper42 can this be merged, now that chronograf is fixed? |
nodejs 16 is an LTS version and nodejs-lts version 12 is EOL
nodejs-lts is now merged to nodejs
Nodejs versioning says that every even release (12, 14, 16, 18) is an LTS release. The
nodejs
package currently uses version 16 which is a supported LTS version,nodejs-lts
uses version 12 which is EOL and very old. Many packages use nodejs-lts for building, but then depend on the nodejs virtual package which defaults to nodejs, many packages don't work with old nodejs-lts and people couldn't have both installed. If we need to, we can always split nodejs-lts again, but right now I don't see a reason to do so. Alpine merged their nodejs-lts package to nodejs and provides nodejs-current for the latest version for development.TODO:
Testing the changes