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.
Fails with versions like "nightly" and "latest"
See original GitHub issuelicense-report just tells me skipping package@nightly (invalid semversion) for any version that isn’t parsable as a semver.
But why does it need the version anyway?
npm accepts these “versions”, so it seems like license-report should as well.
Thank you!
Issue Analytics
- State:
- Created 2 years ago
- Comments:21
Top Results From Across the Web
Unable to do any encodes with latest Nightly versions - Windows
Problem description: Upgraded to latest Nightly. ... Have installed both x86 and x64 versions of what I think I need (Microsoft Windows ...
Read more >Substrate error in both nightly & stable versions - Stack Overflow
1 Answer 1 ... This is a problem exclusively found on windows. If you delete the OK(()) on line #502 the error should...
Read more >Firefox Nightly Error Collection - Mozilla Support
Firefox Nightly automatically collects and sends Mozilla information about JavaScript errors that occur within the browser itself (not on web pages).
Read more >November 2022 (version 1.74) - Visual Studio Code
Learn what is new in the Visual Studio Code November 2022 Release (1.74) ... You can download the nightly Insiders build and try...
Read more >Troubleshoot pipeline runs - Azure DevOps - Microsoft Learn
My pipeline is failing on a command-line step such as MSBUILD. It is helpful to narrow whether a build or release failure is...
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
Fixed in next release based on pr #65.
looks like we should promote you to head of project QA 😉
But seriously: that’s definitely a bug, so please create an issue for this and I will fix it - it is just a small code change.