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.

check-node-version --node '>=6.0.0' .... Invalid comparator

See original GitHub issue

Just after i fixed this issue #426 i got this new one with the next command npm start

E:\SW\Developement\formio>npm start

> formio@1.20.0 start E:\SW\Developement\formio
> npm run version && node main.js

npm WARN invalid config loglevel="notice"

> formio@1.20.0 version E:\SW\Developement\formio
> check-node-version --node '>=6.0.0'

E:\SW\Developement\formio\node_modules\semver\semver.js:678
    throw new TypeError('Invalid comparator: ' + comp);
    ^

TypeError: Invalid comparator: '
    at Comparator.parse (E:\SW\Developement\formio\node_modules\semver\semver.js
:678:11)
    at new Comparator (E:\SW\Developement\formio\node_modules\semver\semver.js:6
62:8)
    at E:\SW\Developement\formio\node_modules\semver\semver.js:828:12
    at Array.map (native)
    at Range.parseRange (E:\SW\Developement\formio\node_modules\semver\semver.js
:827:13)
    at Range.<anonymous> (E:\SW\Developement\formio\node_modules\semver\semver.j
s:769:17)
    at Array.map (native)
    at new Range (E:\SW\Developement\formio\node_modules\semver\semver.js:768:40
)
    at E:\SW\Developement\formio\node_modules\check-node-version\index.js:119:32

    at module.exports (E:\SW\Developement\formio\node_modules\map-values\index.j
s:9:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! formio@1.20.0 version: `check-node-version --node '>=6.0.0'`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the formio@1.20.0 version script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Mourad\AppData\Roaming\npm-cache\_logs\2017-10-14T23_22_53
_748Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! formio@1.20.0 start: `npm run version && node main.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the formio@1.20.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Mourad\AppData\Roaming\npm-cache\_logs\2017-10-14T23_22_53
_819Z-debug.log

E:\SW\Developement\formio>

Any help ?

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:5

Top GitHub Comments

5reactions

r04drunn3rcommented, Nov 7, 2017

The problem seems to be with the single quote in the package.json.

Replace "check-node-version --node '>=6.0.0'" with "check-node-version --node \">=6.0.0\""

0reactions

toddukcommented, Nov 30, 2017

I reported this back in July as issue #380 but didn’t include the text of the error so it wasn’t as easily searchable as it should have been, apologies.

Top Results From Across the Web

Npm install fails due to invalid version - Stack Overflow

So as part of some work I'm doing, I am trying to get the packages we use in our application up to the...

check-node-version - npm Package Health Analysis - Snyk

Ensure you're using the healthiest npm packages. Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice.

package.json - rouch/Cypress - NotABug.org

Cypress - Fast, easy and reliable testing for anything that runs in a browser.

package.json · 汉哥儿/shields - Gitee.com

"check-node-version": "^4.0.3",. "chrome-web-store-item-property": "~1.2.0", ... "babel-plugin-istanbul": "^6.0.0",. "babel-preset-gatsby": "^0.4.8",.

Hírek, események - RisingStack Engineering

... the Node.js DNS library which can lead to the output of wrong hostnames ... deps: update llhttp to 6.0.0; deps: upgrade npm...