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.
Failed to read source code from /vercel/path0/_virtual_~icons/mdi/instagram.jsx
See original GitHub issueI get this when building on Vercel, and sometimes locally (using Nextjs). Redeploying usually fixes the issue
./_virtual_~icons/mdi/instagram.jsx
--
17:44:39.823 | Error: Failed to read source code from /vercel/path0/_virtual_~icons/mdi/instagram.jsx
17:44:39.824 |
17:44:39.824 | Caused by:
17:44:39.824 | No such file or directory (os error 2)
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Failed to read source code from `amp-dev.js` · Issue #31812 ...
10 and I got a file not found error of amp-dev.js . Expected Behavior. No error. To Reproduce. yarn init -y; yarn set...
Read more >How to Read React Errors (fix 'Cannot read property of ...
Got an error like this in your React component? Cannot read property `map` of undefined. In this post we'll talk about how to...
Read more >React JSX file giving error "Cannot read property ...
To import React do import React from 'react' You add brackets when the thing you are importing is not the default export in...
Read more >How to Solve the Chunk Load Error in JavaScript - Rollbar
Whenever there's an error observed in dynamically fetching helper JavaScript files known as Chunks, a ChunkLoad Error is thrown.
Read more >Suspense for Data Fetching (Experimental) - React
Even with await , asynchronous code is often error-prone. Suspense feels more like reading data synchronously — as if it were already loaded....
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
Same here. Super annoying. Have to remove node_modules and reinstall every time this happens.
encountered repeatly. I remove dir node_modules and tentatively remove this webpack config
cacheDirectory: true.hope it go well without this error.