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.
What is going on with the published 2.0.0?
See original GitHub issueerror An unexpected error occurred: "https://registry.yarnpkg.com/nomnom/-/nomnom-2.0.0.tgz: Request failed \"404 Not Found\"".
NPM is saying the latest available version is 1.8.1 from 3 years ago, but also shows this as of today:
'2.0.0': '2018-02-17T00:32:37.653Z'
Somehow this bad release (no tarball exists for 2.0.0) is being installed in a subdependency.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:5
Top Results From Across the Web
Resilience4j 2.0.0 Delivers Support for JDK 17 - InfoQ
Resilience4j 2.0.0 succeeds version 1.7.1, released in June 2021, and is the first major release since version 1.0.0 in September 2019.
Read more >Apache Kafka 2.0.0 has just been released | Packt Hub
Apache Kafka 2.0.0 has been released. It features a wide range of updates and changes that will make the software more secure and...
Read more >Version 2.0.0 released. - Eclipse Mosquitto
The Mosquitto project is happy to announce the release of version 2.0! This is a big change with breaking behaviour changes in the...
Read more >Published POM for 2.0.0 is invalid · Issue #581 - GitHub
Resolving from jcenter gives this error: > Could not resolve com.microsoft.azure:applicationinsights-core:2.0.0.
Read more >Debezium 2.0.0.Final Released
In this section, we're going to dive into the changes with Debezium's core, and discuss how those changes impact all users of Debezium....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Reason by npm https://github.com/zaach/jsonlint/issues/103#issuecomment-367416531
Solution 1 https://github.com/zaach/jsonlint/issues/103#issuecomment-367508416
Solution 2 https://github.com/zaach/jsonlint/issues/103#issuecomment-366452020
I’m experiencing the same issue.