Remove flags, always use null-safe getExports and prefer Meta runtime#297
Merged
Merged
Conversation
Remove safeWebpackModuleExports and preferMetaModuleRuntime flags in favor of unconditionally applying both fixes: - getExports always uses null-safe access (wexports[0]?.exports ?? null) - IIFE checks Meta __debug runtime before __webpack_module_cache__ since Meta's module system is authoritative in Meta's environment Reverts to the simpler IIFE pattern per reviewer feedback.
meta-cla
Bot
added
the
CLA Signed
reshadi
approved these changes
Apr 27, 2026
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.
Remove safeWebpackModuleExports and preferMetaModuleRuntime flags in favor of unconditionally applying both fixes:
Reverts to the simpler IIFE pattern per reviewer feedback.