fix(cjs-build): enable evaluating import.meta in cjs build #1236
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
styfle
reviewed
Nov 20, 2024
Member
styfle
left a comment
There was a problem hiding this comment.
Thanks for the PR!
Please add a test to confirm this is working as expected.
…with pathToFileURL
Contributor
Author
|
@styfle Sorry for taking this long to add the unit tests, it should work as expected now |
|
🎉 This PR is included in version 0.38.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose
A while ago, a PR was merged to disable
import.metaevaluation altogether to support new versions of Webpack. This sometimes causes issues in CJS projects.In the comments, there were some discussions about whether we should have a conditional and keep the previous behavior for CJS builds. This PR addresses exactly this by translating
import.meta.urlto a CJS compatible statement which results to the same output.I have created a comparative build between two projects using the same code and a dependency (@sentry/node) that uses
import.meta.url. You can see the difference in the outputindex.jsBefore the change:
After:
Closes #1019