-
Notifications
You must be signed in to change notification settings - Fork 473
Upgrading/removing dependency to npm-run-all
#306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
enhancement
New feature or request
Comments
I am using https://github.com/open-cli-tools/concurrently as an alternative. Looks good to me so far. |
ghost
pushed a commit
to stanislavmihaylov/vue-bootstrap
that referenced
this issue
Oct 4, 2023
* chore(deps): update dependency lint-staged to v14 (vuejs#329) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency chromedriver to v115 (vuejs#324) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update all non-major dependencies (vuejs#323) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore: add npm and node badge (vuejs#330) * fix: remove `transformMode` from vitest config It's no longer needed in vitest 0.34: > By default, tests with `jsdom` or `happy-dom` use `web` transform mode https://github.com/vitest-dev/vitest/releases/tag/v0.34.0 * chore: import both `mergeConfig` and `defineConfig` from `vitest/config` With the typing fix in Vitest 0.34, it is again possible to use `defineConfig` and `mergeConfig` from the `vitest` package. * feat: add VSCode extension recommendations (vuejs#325) * 3.7.3 * chore: update snapshot * chore: add `rel="noopener"` to the link to `Cypress Component Testing` (vuejs#333) * chore(deps): update all non-major dependencies (vuejs#331) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency chromedriver to v116 (vuejs#332) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency cypress to v13 (vuejs#336) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update actions/checkout action to v4 (vuejs#340) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update all non-major dependencies (vuejs#339) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore: add playground directory to prettierignore The code is generated so it makes no sense to format it. * style: format * chore: dependency maintenance * feat: replace npm-run-all with npm-run-all2 https://www.npmjs.com/package/npm-run-all2 It is a maintained fork of npm-run-all, which is not maintained anymore. Both maintainers of the fork also maintain some other popular packages, so I consider it a safe replacement. Another popular alternative is [concurrently](https://www.npmjs.com/package/concurrently). But [its size](https://packagephobia.com/[email protected]) is too big, I think it would be an overkill. Closes vuejs#306 * fix(config/typescript): pass build arguments to build-only command (vuejs#338) * 3.7.4 * chore: update snapshot * chore: don't ignore zx updates Now we are in the same supported Node.js version range as zx, we can safely upgrade it. * chore: also check for typescript updates with renovate * feat: replace npm-run-all with npm-run-all2 (vuejs#343) * chore(deps): update all non-major dependencies (vuejs#344) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency typescript to ~5.2.0 (vuejs#345) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency chromedriver to v117 (vuejs#346) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * 3.7.5 * chore: update snapshot --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: btea <[email protected]> Co-authored-by: Haoqun Jiang <[email protected]> Co-authored-by: zhhbstudio <[email protected]> Co-authored-by: 汪心禾 <[email protected]> Co-authored-by: Alex <[email protected]> Co-authored-by: Cédric Exbrayat <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a new vue project with
npm init vue@latest
and by checking typescript support, it automatically brings the package npm-run-all. However, this package did not received any update since 2018 (and suffers from a moderate vulnerability viasemver
). Maybe would it be best to move from it, or finding alternatives ?Thank you!
The text was updated successfully, but these errors were encountered: