Source maps cannot be loaded by Chrome DevTools

[d3lm]

When I am serving a specific directory the devtools always complain that the source maps couldn't be loaded. That also makes sense cause Chrome will try to fetch those relative to directory that is served, meaning it looks for source maps in app://-/Users/... and obviously it cannot find them there, cause that path is not a correct path to the node modules where the source maps are located. Any idea what I could do to fix this?

---

IssueHunt Summary

Backers (Total: $40.00)

• issuehunt ($40.00)

Become a backer now!

Or submit a pull request to get the deposits!

Tips

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on IssueHunt to raise funds.

---

IssueHunt has been backed by the following sponsors. Become a sponsor

[issuehunt-oss]

@issuehunt has funded $40.00 to this issue.

---

• Submit pull request via IssueHunt to receive this reward.
• Want to contribute? Chip in to this issue via IssueHunt.
• Checkout the IssueHunt Issue Explorer to see more funded issues.
• Need help from developers? Add your repository on IssueHunt to raise funds.

[dedo1911]

Can you please provide more context of what you're trying to do and what's your folder structure?

In my application, I'm using create-react-app and source maps are included in the build output folder. When I point electron-serve to the build output directory everything works fine and sources are mapped correctly in the devtools.

If I've understood correctly, you want to add another folder in the config where to search for source maps. Is that right?