3 of 6 standards met
Describe the issue After upgrading our project to Vite we enabled the new option in to track upcoming breaking changes. Starting the dev server shows multiple warnings coming from : is replaced with . Plugin hook is replaced with . Plugin hook is replaced with . Each warning links to the Vite documentation detailing the new Environment API changes. Reproduction 1. Create a Vue 2.7 project (e.g. via + downgrade to Vue 2). 2. Install Vite and . 3. In add . 4. Run (or ). 5. Observe the future warnings in the terminal. Our actual project is a Vue 2.7 + Ant Design Vue admin dashboard, but the reproduction above should be enough. Expected behavior should migrate to the new Environment-aware hooks (, , etc.) so that enabling emits no warnings. Additional context Vite: @vitejs/plugin-vue2: Node: Package manager: Thanks!
Repository: vitejs/vite-plugin-vue2. Description: Vite plugin for Vue 2.7 Stars: 578, Forks: 62. Primary language: TypeScript. Languages: TypeScript (81.2%), Vue (11.1%), JavaScript (6.8%), HTML (0.7%), CSS (0.1%). License: MIT. Latest release: v2.3.3 (1y ago). Open PRs: 6, open issues: 44. Last activity: 4mo ago. Community health: 62%. Top contributors: yyx990803, sxzz, sapphi-red, haoqunjiang, dev-itsheng, gabrielrbarbosa, zonemeen, linshuohao, bigyifeng, WJCHumble and others.
Last 12 weeks · 0 commits
When using Vue 2 with LightningCSS (via ), the following warning appears: This occurs because LightningCSS doesn't recognize the pseudo as a valid pseudo-class, even though it's a valid Vue.js scoped CSS feature. We can apply the same warning suppression mechanism from vite-plugin-vue to vite-plugin-vue2. The fix suppresses the specific warning about v-deep and deep pseudo-classes in LightningCSS. There is a repo reproduce I'm preparing a PR. References vite-plugin-vue Issue #507 vite-plugin-vue Pull Request #521 Vue Deep Selectors Documentation stackoverflow