Replies: 2 comments 2 replies
-
My issue with that is maintenance. I'm personally ok keeping the warning. I know far too well what those kind of maintenance and monitoring generate as workload and I'd like to avoid it. LTS are maintained for 3 years, which means every 3 year we have to update all engines. Seems quite acceptable compared to every year? |
Beta Was this translation helpful? Give feedback.
-
( Resumption on #6 (comment) ) Just as we keep the possibility of npm7, but the default 'out of the box' is mostly npm8, i personally think, that we should include So keeping node fixed to 16, and adding npm 7 & 8 for now, i don't think there is the necessity to monitor everything @skjnldsv. Node 16 with Npm 7 & 8 works for now, so the only thing that will need a change is if node 16 starts supporting npm 9. And i don't think we need to shoot faster than our shadow: Once this happens, any dev will come up with and we can just add |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
From @korelstar
But this will give warnings, since npm 8 is not compatible to
^7.0.0
. What about settingNPM_VERSION: "^7.0.0 || ^8.0.0"
, then all node@16 installations (e.g. official docker container) will work just out of the box?Beta Was this translation helpful? Give feedback.
All reactions