Update uglify dependency #3662
Merged
Update uglify dependency #3662
+1
−1
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
Apparently we needed to get to v2.4.17 to get the fix for facebook#2247. We shrinkwrapped on the same day but the timing didn't work out so we missed it.
zpao
added a commit
to zpao/react
that referenced
this pull request
Apr 13, 2015
Update uglify dependency
zpao
added a commit
to zpao/react
that referenced
this pull request
Apr 17, 2015
Update uglify dependency
zpao
added a commit
to zpao/react
that referenced
this pull request
Apr 18, 2015
Update uglify dependency
This was referenced Aug 18, 2021
This was referenced Sep 12, 2021
This was referenced May 13, 2022
This was referenced Nov 27, 2023
This was referenced Mar 22, 2024
This was referenced May 13, 2024
This was referenced May 22, 2024
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.
Apparently we needed to get to v2.4.17 to get the fix for #2247. We
shrinkwrapped on the same day but the timing didn't work out so we missed it.