Rollup freeze: false#12879
Merged
Merged
Conversation
Collaborator
|
I think maybe we could leave it on in development. This discourages our internal code from trying to override the modules that are currently exposed (but won't be in the future). Thus reducing the surface area for things we might need to clean up. |
Contributor
Author
|
That seems reasonable. I'll update the diff. |
|
ReactDOM: size: -0.1%, gzip: -0.1% Details of bundled changes.Comparing: 60853f0...70d25b5 react-dom
Generated by 🚫 dangerJS |
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
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.
Rollup freezes several imported modules in our current bundle. This doesn't really seem necessary, so I've updated the Rollup config to not freeze bundles for the production build.
react-dom.development.jsdiff(no diff)
react-dom.production.min.jsdiffAfter running both files through Prettier.