This repository has been archived by the owner on Sep 2, 2022. It is now read-only.
Upgrade npm-run
#4373
Closed
Upgrade npm-run
#4373
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
Avoid a vulnerability in older version of `npm-run`'s `[email protected]`: https://nvd.nist.gov/vuln/detail/CVE-2017-16024
|
|
|
Hi @tianhuil As discussed in prisma/prisma#3723 (comment) upgrading it to v5 will break windows support. RIght now we are waiting for for timoxley/npm-run#21. But this vulnerability only occurs in development so I think we are safe waiting rather than breaking windows build. We are already planning for the next iteration of our CLI for prisma 2 and in that, we will avoid using this altogether. |
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.
Avoid a vulnerability in older version of
npm-run's[email protected]: https://nvd.nist.gov/vuln/detail/CVE-2017-16024