Open vladimiry opened 3 years ago
On our side, we only validate things for the latest LTS (v14). Compat with the new LTS will be done before the v16 becomes the LTS. It should be available during summer I think :thinking:
(Depends if the support breaks something for v14 or we can have it for both, LTS is more important than v16)
Yep, I understand the LTS matter. Just wanted to highlight that updating sharp
version will fix the issue when running on node.js v16.
Currently
npm ci
step gets failed on node.js v16 during rebuildingsharp
native module.Upgrading
sharp
version inproton-pack#favicons-webpack-plugin#favicons
andproton-pack#sharp
chains is likely going to help, see https://github.com/lovell/sharp/issues/2611.