Skip to content
New issue

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

Incorrect latest version #24

Open
bartbutenaers opened this issue Feb 25, 2022 · 1 comment
Open

Incorrect latest version #24

bartbutenaers opened this issue Feb 25, 2022 · 1 comment

Comments

@bartbutenaers
Copy link

Hi guys,

Based on this discussion on Discourse.

My node-red-contrib-xterm/ node uses these dependencies:

 "dependencies": {
    "xterm": "^4.17.0",
    "xterm-addon-fit": "^0.5.0",
    "node-pty-prebuilt-multiarch": "^0.10.1-pre.4"
 },

Which results in following scorecard warning:

image

Running the node-red-dev tool manually gives me some more information, about what is wrong:

node-pty-prebuilt-multiarch is not at latest version, package.json specifies: ^0.10.1-pre.4, latest is: 0.10.0

Which is weird, because I use the latest version of the node-pty-prebuilt-multiarch package:

image

However it seems that the npm-check library passes the wrong latest version to node-red-dev:

image

Thanks !!!
Bart

@mike-feldmeier
Copy link

Not a dev, but came across this trying to find reasons for the issue I'm running into.

The node-red-dev tool is correct. The "latest" is always the the latest stable version (https://docs.npmjs.com/about-npm-versions). Anything with a prerelease tag is not considered stable (https://docs.npmjs.com/cli/v6/using-npm/semver#prerelease-tags). So, according to the version history list you provided, 0.10.0 is the latest stable version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants