We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
It's August 2024 and I'm also running into this same issue.
Sorry, something went wrong.
I am not following this issue anymore I have since migrated off of BigCommerce so this is not longer a bug I care about.
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: