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.
ESM builds should substitute `__filename` and `__dirname` references in CommonJS
See original GitHub issueFeature request
What is the expected behavior?
When building an ESM build in Webpack, free __filename and __dirname references in CommonJS files should be supported.
What is motivation or use case for adding/changing the behavior?
See eg https://github.com/vercel/ncc/issues/749 for an ncc bug here.
How should this be implemented in your opinion?
The referencing could do relative path logic or not. That shoudl likely be configurable. In the base case for CommonJS the __filename value would be the output file __filename value which seemed to work in some scenarios.
One could just define CJS free __filename references as fileURLToPath(import.meta.url) in the Webpack bundle.
Are you willing to work on this yourself? no
Issue Analytics
- State:
- Created 2 years ago
- Reactions:8
- Comments:11 (5 by maintainers)
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
Bump, there’s a PR by @vankop still open https://github.com/webpack/webpack/pull/14247
@fregante , @vankop In my case, I’m bundling everything (except a *.node file) into one
index.bundle.js, and so node won’t allow usage of__dirname/__filenamefrom dependencies since they are now top-level. At least that’s what I think is happening. Correct me if I’m wrong.