Make sure node_modules/web-animations-js is patched after gulp update-packages
#13199
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.
In #6189, @dvoytenko added a function
patchWebAnimations()
togulpfile.js
, which writes the filenode_modules/web-animations-js/web-animations.install.js
. However, this function was being called in the global scope ofgulpfile.js
, and would therefore run before anygulp
task was executed.This poses a problem when
gulp update-packages
is run as a prerequisite togulp
, and happens to updatenode_modules
, sinceweb-animations.install.js
is patched beforenode_modules/web-animations-js
is potentially overwritten byyarn
.This PR eliminates the problem by moving the call to
patchWebAnimations()
from the global scope ofgulpfile.js
to just before the extensions are built as part of the gulp build process.Fixes #13177