Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Supported engines: npm

See original GitHub issue

Describe the bug Package “core” does not support npm?

To Reproduce Steps to reproduce the behavior:

Install core or react package
Get following message from npm:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@use-cookie-consent/core@0.3.3',
npm WARN EBADENGINE   required: { node: '>=12', npm: '<0', yarn: '^1' },
npm WARN EBADENGINE   current: { node: 'v14.18.1', npm: '8.1.1' }
npm WARN EBADENGINE }

Expected behavior No message like this

Desktop (please complete the following information):

OS: WSL on Windows 10

Additional context Is there a reason for saying npm <0? Otherwise it seems to be easy to fix 😉

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

cmmdmxcommented, Mar 5, 2022

Looks like the warning is gone, thank you!

1reaction

cmmdmxcommented, Mar 1, 2022

Excluding package-lock via git seems to be perfectly fine 👍

Top Results From Across the Web

package.json

This is a set of config values that will be used at publish-time. It's especially handy if you want to set the tag,...

Node Engines: Helping Developers Everywhere Avoid ...

Node engines are a little discussed (but in my opinion pretty critical) configuration that can be specified in your package.json file that tells ......

Node engine 8.x or 10.x in package.json

json to accept both 8 and 10 version. I tried to type this: "engines": { "node": "8.x|10.

Configuring your application's dependencies

Use the engines keyword in the package.json file to specify the Node.js version that you want your application to use. You can also...

package.json: engines & engineStrict - and how to use them

Yes, remember that npm stands for Node Package Manager. The engines-field is also in the package.json file. I first thought and hoped that...