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.
Absolute system paths in js from output bundle
See original GitHub issueAfter building production package with npm run build, I opened produced js file and found absolute system paths like this:
t.register(a,"default","D:/texts/Sources/react-webpack-babel/src/components/Sample.jsx")
Why are there absolute paths? How can I remove/fix them?
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (4 by maintainers)
Top Results From Across the Web
reactjs - Absolute system paths in js from output bundle - Stack ...
After building production package with npm run build , I opened produced js file and found absolute system paths like this:.
Read more >[Bug] Absolute paths leaking in the bundle #1303 - GitHub
Absolute paths are found in the exported bundles. This is surprising, can leak information about your build system, and will cause webpack ...
Read more >Output - webpack
The bundle is written to the directory specified by the output.path option. For a single entry point, this can be a static name....
Read more >Node.js File Paths
How to interact with file paths and manipulate them in Node.js. ... Every file in the system has a path. On Linux and...
Read more >Importing with Absolute Paths in JavaScript/TypeScript using ...
How to use absolute paths in JavaScript and TypeScript to improve your import statements, using the right webpack configuration.
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
I see, Have you tried removing react-hot-loader and see if it fixes the problem? In that case we’ll know where to look
This has been fixed in the new release