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.

Error: Couldn't resolve version spec %s: %s

See original GitHub issue

First of all, thank you very much for very useful application!

Now I got an error in nodeist@0.8.2 in Windows 8.1. I have installed node with version 4.4.7 with nodist.

When I command node in the directory, then I got an error Sorry, there's a problem with nodist. Couldn't resolve version spec %s: %s >=4.0.0 <7.0.0 improper constraint: >=4.0.0 <7.0.0.

The directory have package.json file which includes key "engines": {"node": ">=4.0.0 <7.0.0"}, it might make problem. When I removed the line "engines": {"node": ">=4.0.0 <7.0.0"}, then the command node works well.

Issue Analytics

State:
Created 7 years ago
Comments:17

Top GitHub Comments

6reactions

marcelklehrcommented, Jul 14, 2016

Mh. That’s a bug in the semver lib for the shims.

As an intermediate fix you can override local switching with env switching: you can set the desired version using nodist env x.x.x

On July 14, 2016 11:25:39 AM CEST, Jack Cuthbert notifications@github.com wrote:

Colleagues of mine also having the same issue on Windows 10. Removing <7 solved it for them: "engines": {"node": ">=4"} should work until this is resolved.

You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/marcelklehr/nodist/issues/155#issuecomment-232613714

Sent from my Android device with K-9 Mail. Please excuse my brevity.

3reactions

Mikk36commented, Sep 9, 2016

Deleted .node-version file, problem gone.

Top Results From Across the Web

Error: Couldn't resolve version spec %s: %s · Issue #155

When I command node in the directory, then I got an error Sorry, there's a problem with nodist. Couldn't resolve version spec %s:...

How to solve this problem Error: Couldn't resolve the package?

I couldn't manage to make it work on the main package, so I imported Equatable in this private sub-package, exported (using export keyword)...

3 ways to solve java.lang.NoClassDefFoundError in Java J2EE

This is the most common error in Java development along with java.lang. ... NoClassDefFoundError: Could not initialize class on other places.

Troubleshoot Content Distribution issues - Microsoft Learn

This article discusses how to troubleshoot common content distribution issues. Original product version: Configuration Manager current branch, ...

Online Error Reference Material - SSA

Online Error Reference Material. To help resolve error conditions that prevented Social Security from processing your wage report, view the file on your...