You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use Vite V2.7.2 and this issue is still present. When building and watching changes with the command vite build --watch it ignores scoped css in the same component. After I restart with vite build --watchit uses scoped css again, but after any change in the template part of the component, it will ignore scoped css style. If I change something in the style part of the component it will use scoped css again. Additionally it doesn't show changes without refreshing the browser screen when using vite build --watch command.
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
I’m running into this also. It looks like —watch is building the component with a new data-v value, but not generating a new css file so the mismatched data-v attributes result in the scoped css styles not getting applied.
Hello @Dagge1. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.
Describe the bug
I use Vite V2.7.2 and this issue is still present. When building and watching changes with the command
vite build --watch
it ignores scoped css in the same component. After I restart withvite build --watch
it uses scoped css again, but after any change in the template part of the component, it will ignore scoped css style. If I change something in the style part of the component it will use scoped css again. Additionally it doesn't show changes without refreshing the browser screen when usingvite build --watch
command.Reproduction
no
System Info
Used Package Manager
npm
Logs
No response
Validations
The text was updated successfully, but these errors were encountered: