This repository has been archived by the owner on Dec 14, 2023. It is now read-only.
Workaround for UglifyJs madness #337
Closed
Conversation
This file contains 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
mishoo/UglifyJS#2054 shrinkwrap was an issue because of cp-translations bumping on deploy npm 3 is dodgy on node 0.10 and would have forced an upgrade on all microservices so here is a dodgy workaround
Wardormeur
force-pushed
the
bugfix/uglifyjs-faulty-version
branch
from
8c983c7
to
8b2741f
Compare
|
this shouldnt be needed with 2.8.29 released mishoo/UglifyJS@0af80ec |
|
Good to see i can avoid this. 👍 |
|
Should be able to close this PR now, right? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
mishoo/UglifyJS#2054
shrinkwrap was an issue because of cp-translations bumping on deploy
npm 3 is dodgy on node 0.10 and would have forced an upgrade on all microservices (same instance)
so here is a dodgy workaround