Open RightFootConsulting opened 8 months ago
npm install @bigcommerce/stencil-utils after running this we get $ npm install @bigcommerce/stencil-utils npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@bigcommerce/stencil-utils@6.15.1', npm WARN EBADENGINE required: { node: '>=14.0.0 <19.0.0' }, npm WARN EBADENGINE current: { node: 'v20.11.0', npm: '10.2.4' } npm WARN EBADENGINE }
up to date, audited 1763 packages in 5s
137 packages are looking for funding run npm fund for details
npm fund
24 vulnerabilities (21 moderate, 3 high)
To address issues that do not require attention, run: npm audit fix
To address all issues (including breaking changes), run: npm audit fix --force
Run npm audit for details.
npm audit
You should at least make sure you support the latest node LTS plunking security vulnerabilities into apps is not good engineering.
It's August 2024 and I'm also running into this same issue.
npm install @bigcommerce/stencil-utils after running this we get $ npm install @bigcommerce/stencil-utils npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '@bigcommerce/stencil-utils@6.15.1', npm WARN EBADENGINE required: { node: '>=14.0.0 <19.0.0' }, npm WARN EBADENGINE current: { node: 'v20.11.0', npm: '10.2.4' } npm WARN EBADENGINE }
up to date, audited 1763 packages in 5s
137 packages are looking for funding run
npm fund
for details24 vulnerabilities (21 moderate, 3 high)
To address issues that do not require attention, run: npm audit fix
To address all issues (including breaking changes), run: npm audit fix --force
Run
npm audit
for details.You should at least make sure you support the latest node LTS plunking security vulnerabilities into apps is not good engineering.