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.
Command line: Dependencies aren't re-indexed after npm update.
See original GitHub issueWhen node_modules dependency is updated, and the command line utility subsequently run, ExportsStorage#needsUpdate fails to flag the dependency’s main file as needing to be reindexed, so new exports aren’t found.
The root cause appears to be that needsUpdate is receiving the wrong mtime from ModuleFinder: when ModuleFinder expands files (in expandFiles), it flags each dependency file with the mtime of the root package.json, here. It should instead go get the mtime of the dependency’s main file. (That whole stack is already super asynchronous, so at least it shouldn’t take any external rearchitecting to fix.)
Edit: added link to the root cause.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
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
I need to clean up a few things before merging, but I agree that this makes things slightly better.
Fixed in 50a9fa (#386)