question-mark
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.

Engine syntax incorrect

See original GitHub issue

I cannot install the latest v7 on node 16 at the moment. NPM is complaining about incompatible version:

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: superagent@7.0.0
npm ERR! notsup Not compatible with your version of node/npm: superagent@7.0.0
npm ERR! notsup Required: {"node":">=6.4.0 <13|>=14"}
npm ERR! notsup Actual:   {"npm":"8.3.0","node":"v16.13.0"}

I believe the issue is the syntax used in the engines block in the package.json

I think instead of:

  "engines": {
    "node": ">=6.4.0 <13|>=14"
  },

it should be:

  "engines": {
    "node": ">=6.4.0 <13||>=14"
  },
``` (double pipe instead of single)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:9 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
nbezzalacommented, Jan 8, 2022

This is still an issue.

$ npm install superagent npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: ‘superagent@7.0.1’, npm WARN EBADENGINE required: { node: ‘>=6.4.0 !13’ }, npm WARN EBADENGINE current: { node: ‘v17.3.0’, npm: ‘8.3.0’ } npm WARN EBADENGINE }

up to date, audited 38 packages in 2s

9 packages are looking for funding run npm fund for details

found 0 vulnerabilities

2reactions
textbookcommented, Jan 11, 2022

To express “v6.4.0 or newer, excluding v13” you want e.g. >=6.4.0 <13 || >=14; you can try these out on https://semver.npmjs.com/.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Syntax Error or Engine Error? - Stack Overflow
Hello everyone I'm trying to create a page to create a db from a php page. But at the time of running the...
Read more >
Engine syntax incorrect · Issue #1660 · ladjs/superagent · GitHub
I believe the issue is the syntax used in the engines block in the package.json. I think instead of: "engines": { "node": ">=6.4.0...
Read more >
FileNet Content Engine Incorrect syntax error during AddOn ...
The incorrect syntax is due to the "ON Index" part of the sql statement. The customer had created a filegroup in MS SQL...
Read more >
View topic - CE 7.3 Script Editor No Syntax Error - Cheat Engine
If script has a syntax error, it errors with "Not all code is injectable (Access violation)" instead of showing the line number and...
Read more >
SyntaxError - JavaScript - MDN Web Docs
The SyntaxError object represents an error when trying to interpret syntactically invalid code. It is thrown when the JavaScript engine encounters tokens or ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found