Conversation
…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 <4497128+Alex-Sokolov@users.noreply.github.com>
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)
Fixes the issue caused by babel/babel#12989
…`--no-unsafe-inline` flag (#6422)
Default Cypress version is now v7
As Vue 3 does not, and likely will not support IE11. vuejs/rfcs#294
…and cli-plugin-e2e-nightwatch (#7158) Co-authored-by: blzsaa <blzsaa@users.noreply.github.com>
…ring upgrade (#7167) Co-authored-by: blzsaa <blzsaa@users.noreply.github.com>
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
…7443) Fixes vue v3.5.19 compatibility
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )