Build: Update dependencies, keep legacy jQueries in the repository #134
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
1a42d10 to
ded9161
Compare
Apart from updating npm dependencies, we now keep legacy jQuery versions - ones that were not published to npm - directly in the `external-legacy-source` folder instead of installing GitHub repositories as npm packages. The `external` directory is no longer kept in the repository; it's generated on the fly instead.
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.
Apart from updating npm dependencies, we now keep legacy jQuery versions - ones that were not published to npm - directly in the
external-legacy-sourcefolder instead of installing GitHub repositories as npm packages.This will resolve some vulnerability reports about dev dependencies.