refactor!: avoid import.meta polyfill - #3213
Merged
Merged
Conversation
import.meta polyfill
Member
|
nodejs/node#57804 is supported in LTS now (since Node 22.18.0) 👏🏻 |
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
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.
We have introduced a polyfill for
import.metain nitro v2 for platform compatibility however with advancements of runtimes, there will be more leverages of platform nativeimport.meta.Downside of depending on platform
import.metais that the value differs between source and bundle.For internal use of serveStatic (to resolve public dir relative to server entry) a lightweight
globalThis.__nitro_meta__injection is used instead. (hopefully one day we can useimport.meta.maininstead: nodejs/node#49440)