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
After upgrading from v4 to v5 I am receiving lots of error related to undefined variables errors only in production build.
No config change were made only npm package version upgrade.
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 vuejs/core instead.
It seems to be treating all my scss files as individual entry points and or trying to compile them individually even if they are not referenced by any react code.
I was able to rename one of the files to a random name 99common99.scss and it's still trying to compile it.
When I create a new project i'm not seeing it behave the same way.
Hello @nsmithdev. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with needs reproduction will be closed if they have no activity within 3 days.
Describe the bug
After upgrading from v4 to v5 I am receiving lots of error related to undefined variables errors only in production build.
No config change were made only npm package version upgrade.
Before: "vite": "^4.4.8",
After: "vite": "^5.0.0",
I can still compile with scss manually with command:
.\node_modules\.bin\sass --load-path=node_modules .\src\assets\styles\app.scss
Did something change with how scss variable scoping works etc? I can't find anything in the release notes.
I wanted to check if there was a simple solution before creating a reproduction.
I'll post it soon as I can create one.
Reproduction
a
Steps to reproduce
No response
System Info
Used Package Manager
npm
Logs
error during build:
Error: Undefined variable.
Validations
The text was updated successfully, but these errors were encountered: