-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
npm error #209
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
Comments
The reason that we can't use the regular jsonlint package from npm is that there is a bug related to using it via browserify: zaach/jsonlint#57. The official package seems not to be maintained at all :(. To solve this I forked the library, created a fix for it, and link to that fork from jsoneditor. When does this error occur? |
On my side this error occur when executing the npm installation
Fails on retrieving the jsonlint package, so installation fails. Really strange as I did succeed to install it on another computer. |
I fixed the issue on my side by forking your project, cloning it in my project instead of downloading using NPM and modifying the package.json to use the 1.0.0 version of jsonlint. It is not ideal as it is part of the installation process of my current project. Any ideas/clues how to fix that ? |
Maybe you have a different version of npm or something? I've already removed the dependency on my forked version of |
The just released v5.0.0 has no longer a dependency on this raw git url of jsonlint, I suppose this issue is resolved now. |
error is as follows
Error: No compatible version found: jsonlint@'josdejong/jsonlint#85a19d7'
Looking at package.json changes i see jsonlint went from dev dependancy to dependancy, and then to this lockfile.
Any reason not to remove the lock file linking back to jsonhint?
The text was updated successfully, but these errors were encountered: