-
Notifications
You must be signed in to change notification settings - Fork 0
[pull] dev from vuejs:dev #26
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
base: dev
Are you sure you want to change the base?
Conversation
Hard-Coded Secrets (5)vue-cli/docs/.vuepress/config.js Line 58 in 2d3116e
vue-cli/docs/zh/guide/mode-and-env.md Line 106 in 2d3116e
More info on how to fix Hard-Coded Secrets in General. Insecure Use of Regular Expressions (31)
vue-cli/packages/@vue/cli/lib/add.js Line 37 in 2d3116e
vue-cli/packages/@vue/cli/lib/options.js Line 53 in 2d3116e
vue-cli/packages/@vue/cli/lib/ui.js Line 10 in 2d3116e
Line 152 in 2d3116e
vue-cli/scripts/verifyCommitMsg.js Line 5 in 2d3116e
vue-cli/packages/@vue/cli/lib/Creator.js Line 342 in 2d3116e
More info on how to fix Insecure Use of Regular Expressions in Javascript. Insecure File Management (188)
vue-cli/packages/@vue/cli-ui/src/i18n.js Line 64 in 2d3116e
vue-cli/packages/@vue/cli/bin/vue.js Line 30 in 2d3116e
vue-cli/packages/@vue/cli/bin/vue.js Line 31 in 2d3116e
vue-cli/packages/@vue/cli/lib/GeneratorAPI.js Line 445 in 2d3116e
vue-cli/packages/@vue/cli/lib/GeneratorAPI.js Line 482 in 2d3116e
vue-cli/packages/@vue/cli/lib/GeneratorAPI.js Line 484 in 2d3116e
vue-cli/packages/@vue/cli/lib/GeneratorAPI.js Line 519 in 2d3116e
vue-cli/packages/@vue/cli/lib/Upgrader.js Line 102 in 2d3116e
vue-cli/packages/@vue/cli/lib/config.js Line 35 in 2d3116e
vue-cli/packages/@vue/cli/lib/config.js Line 68 in 2d3116e
vue-cli/packages/@vue/cli/lib/create.js Line 32 in 2d3116e
vue-cli/packages/@vue/cli/lib/inspect.js Line 21 in 2d3116e
vue-cli/packages/@vue/cli/lib/options.js Line 94 in 2d3116e
vue-cli/packages/@vue/cli/lib/options.js Line 96 in 2d3116e
vue-cli/packages/@vue/cli/lib/options.js Line 127 in 2d3116e
Line 8 in 2d3116e
Line 19 in 2d3116e
Line 43 in 2d3116e
Line 47 in 2d3116e
Line 48 in 2d3116e
Line 52 in 2d3116e
Line 53 in 2d3116e
vue-cli/scripts/buildEditorConfig.js Line 96 in 2d3116e
vue-cli/scripts/buildEditorConfig.js Line 118 in 2d3116e
vue-cli/scripts/buildEditorConfig.js Line 119 in 2d3116e
vue-cli/scripts/buildEditorConfig.js Line 121 in 2d3116e
Line 23 in 2d3116e
Line 36 in 2d3116e
Line 41 in 2d3116e
vue-cli/scripts/genChangelog.js Line 23 in 2d3116e
vue-cli/scripts/genChangelog.js Line 24 in 2d3116e
Line 9 in 2d3116e
Line 11 in 2d3116e
Line 15 in 2d3116e
vue-cli/scripts/patchChromedriver.js Line 14 in 2d3116e
Line 90 in 2d3116e
Line 104 in 2d3116e
Line 173 in 2d3116e
Line 181 in 2d3116e
Line 188 in 2d3116e
vue-cli/scripts/verifyCommitMsg.js Line 3 in 2d3116e
More info on how to fix Insecure File Management in Javascript. Information Disclosure (17)vue-cli/packages/@vue/cli-plugin-e2e-cypress/generator/template/tests/e2e/_eslintrc.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-cypress/generator/template/tests/e2e/specs/test.js Line 6 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-nightwatch/generator/template/tests/e2e/_eslintrc.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-nightwatch/generator/template/tests/e2e/specs/test.js Line 10 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-webdriverio/generator/template/tests/e2e/_eslintrc.js Line 1 in 2d3116e
Line 15 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-webdriverio/generator/template/tests/e2e/specs/app.spec.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-webdriverio/generator/template/wdio.local.conf.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-webdriverio/generator/template/wdio.sauce.conf.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-e2e-webdriverio/generator/template/wdio.shared.conf.js Line 14 in 2d3116e
vue-cli/packages/@vue/cli-plugin-router/generator/template-vue3/src/router/index.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-unit-jest/generator/template/tests/unit/example.spec.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli-plugin-unit-mocha/generator/template/tests/unit/example.spec.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli/__tests__/mock-preset-with-async-generator/generator/template/test.js Line 1 in 2d3116e
vue-cli/packages/@vue/cli/__tests__/mock-preset-with-template/generator/template/test.js Line 1 in 2d3116e
More info on how to fix Information Disclosure in Javascript. Insecure Use of Dangerous Function (18)
vue-cli/scripts/buildEditorConfig.js Line 98 in 2d3116e
vue-cli/scripts/patchChromedriver.js Line 8 in 2d3116e
Line 11 in 2d3116e
Line 41 in 2d3116e
More info on how to fix Insecure Use of Dangerous Function in Javascript. Insecure Processing of Data (20)
More info on how to fix Insecure Processing of Data in Javascript. Insecure Use of SQL Queries (6)
More info on how to fix Insecure Use of SQL Queries in Javascript. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
…support in `vue.config.js` (#6355)
…pendencies in `node_modules` (#6354)
Also reverts #6358
Respect the existing 'devtool' when running dev server Fixes #6398
* docs: (ru) config/readme.md update * docs: (ru) eslint.md update * docs: (ru) cli-service.md update * docs: (ru) css.md update * docs: (ru) mode-and-env.md update * docs: (ru) deployment.md update Co-authored-by: Alex Sokolov <[email protected]>
It's messing with the html-webpack-plugin, telling it the wrong hash of the legacy bundle, therefore making the modern mode fallback unusable. (TODO: add a test later)
…ot installed (#6418) Co-authored-by: Haoqun Jiang <[email protected]> closes #6383
Fixes the issue caused by babel/babel#12989
…`--no-unsafe-inline` flag (#6422)
Default Cypress version is now v7
…and cli-plugin-e2e-nightwatch (#7158) Co-authored-by: blzsaa <[email protected]>
…ring upgrade (#7167) Co-authored-by: blzsaa <[email protected]>
Closes #7024 Fixes #7118 I choose to not merge the PR because I don't want add additional ways to configure https for dev server (`--http2` command line argument, `process.env.HTTPS`, etc.) In the current implementation, `spdy` can only be configured by setting `{ devServer: server: { type: 'spdy' } }`. This is a deliberate choice, because SPDY support in Node.js 15+ is broken anyway. I don't want bother refactoring the old code to accommodate this broken feature.
It is only served as a fallback version number when local Chrome version detection failed. Updating the version to the latest may reduce user frustrations when such rare scenarios are encountered. Closes #7203
Fixes #7221 `subscriptions-transport-ws` is also deprecated, we need to move to `graphql-ws` one day. But better deprecatedthan broken.
The dev dependency `@graphql-eslint/eslint-plugin` is causing CI failures in Node.js 12
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
vuejs/eslint-config-prettier#11 I would recommend using the ESLint CLI directly over `@vue/cli-plugin-eslint` at this point. But for users who are stuck with old versions and still read this migration guide, they deserve a working link.
…rect package from npm Thanks to @alxndrsn for finding this issue and the insightful blog post. https://www.alxndrsn.com/2024-08-01-npx-binary-confusion/ Also thanks to @lirantal for his newsletter that brought this issue to my attention. https://www.nodejs-security.com/newsletter/npm-supply-chain-security-prisma-orm-security-fun-nodejs-security-challenges
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )