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.
Response Code 404 (Not Found) with local dependencies
See original GitHub issueHello all,
NO PROBLEM WITH NODE, SEE UPDATE BELOW
I have recently installed Node version 14.19.2 in my WSL. Since upgrading to this version, I can no longer create a licence report because the command returns a 404 Not Found Error.
In another WSL instance with Node version 14.18.2, the creation of the report works perfectly. I have attached 2 screenshots with debug logging.
Can you please take a look at the problem? Downgrading my WSL instance to a version <14.19 is unfortunately not an option.
Many thanks and kind regards Johannes
Output on Node 14.19.2:
Output on Node 14.18.2:
UPDATE
Issue has nothing to do with Node.
I found the problem. I have a local dependency in my package.json file:
... "local-dep": "file:ext/local-dep-2.13.6.tgz", ...
When I remove this dependency the generation of the license report works perfectly.
I also tried it with a colleague in his WSL, who was still using an older version of licence-report. The generation worked perfectly for him.
The output of the generated license-report with the local dependency was like this - which was OK for us:
local-dep,n/a,n/a,n/a
After updating to the current version of license-report, he also got the “404 Not Found” error.
The problem has nothing to do with the Node version. The problem seems to be that license-report in the new version can no longer handle local dependencies. Unfortunately, I had installed different versions of license-report on my WSL instances and therefore immediately suspected that it was due to the Node version.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:12
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s the minimum requirement - I just didn’t expect that there are “invalid” uris in the package-lock.json as I did not think about local dependencies - my fault.
So Step 1 is to catch errors and step 2 is to evaluate local dependencies.
But give me some days - I do not have the time for that the next few hours 😄
Hi @BePo65,
can you please look into this again? The latest version on npm is still 5.0.2. Thank you.
Kind regards Johannes