I have created a temporary solution to this problem here:
Hello again! We just deployed a change that will add Node 16.6 to containers. Due to our 12 hour container cycling schedule, though, it may take up toâŚ12 hours for your projects to be able to use it, so update responsibly!
Thanks very much. The timing of these libraries wasnât ideal but it was going to be troublesome to wait until October. Particularly for people who develop directly on Glitch, it meant they couldnât even begin to migrate their code until then and they are going to encounter a number of âgotchasâ in v13 due to library changesâŚ
Two things. First a confirmation that everything worked. I updated my bot and have had no issues. The other is there was a patch issued for npm and while that doesnât (probably) affect anyone it does mean that everyone using Node 16.6 will get that message. Maybe there is a way you can apply the patch to your containers as well?
npm notice
npm notice New patch version of npm available! 7.20.3 â 7.20.5
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.20.5
npm notice Run npm install -g npm@7.20.5 to update!
npm notice
We only support the version of NPM that comes with the version of Node that youâre using, we donât patch/update those separately. If the version of NPM is causing issues with an LTS version of Node, though, do let us know.
Hello, I would like to know if nodejs 16 was ready, because when I change from 14 to 16, the console tells me that it goes back to 14
I hope to have an answer soon, good day/evening
Hi there - we did set up Node 16 awhile ago. Can you email support@glitch.com with the name of the project so we can confirm that your configuration is correct and see if itâs a bug on our end?
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.