-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
[BUG] --watch Lib Mode style.css not regenerated #3566
Comments
I'm seeing something similar with png files as well (see below). I was seeing this css issue with version 2.3.4 which does not appear to occur with version 2.3.3. With 2.3.3, it's other assets like the logo.png file shown below.
|
Thank you for reporting this. I also came across this issue, for context if that's helpful : I use Vite to build the frontend assets in a legacy Symfony php application. I import all the stylesheets in the entry files, so that they are compiled & "chunked" by the build process (as well as merged with the Tailwind JIT 's own output). I can use dev server in my php app, which is great, by including the VIte client and the raw But sometimes the "flash of unstyled content"; due to importing stylesheets in my entries, is annoying. So sometimes I run my app in a semi-production mode whereby php renders JS/CSS tags using the output files from So that's how I noticed the issue. On first run, |
I didn't like the ever growing dist folder (and sometimes it didn't suffice), so I got around it by using nodemon as my watcher and having nodemon execute a |
Same, I also faced the issue that I had to solve using the |
Same here. If a run |
I believe I am facing the same issue. The first Runlog:
The problem also exists when not emptying out the output-dir:
My vite.config.js: import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
export default defineConfig({
plugins: [vue()],
build: {
outDir: "../dist/ui"
},
}) Env Info: $ node -v
v16.3.0
$ npm -v
7.17.0 package.json ...
"dependencies": {
"pinia": "^2.0.0-alpha.19",
"scorm-again": "^1.6.0",
"vue": "^3.0.5"
},
"devDependencies": {
"@vitejs/plugin-vue": "^1.2.3",
"@vue/compiler-sfc": "^3.1.1",
"vite": "^2.3.7"
} |
I faced the same issue. First build:
Modify app.tsx for example:
Modify global.less for example:
Although css file has been regenerated, but IT HAS ONLY global.less RECOMPILED, other less files are not in it at all. |
@AlishaHawkward would you check your project with this PR #3747? It should also fix this bug. |
Thank you very much! Works here 👍 Probably unrelated but does anyone else sometimes have |
Describe the bug
If a JS file is specified as the target in Lib Mode, CSS / SCSS can also be imported in the JS file. This CSS file is taken during the first creation and generates a style.css. But if you add a --watch parameter, new files are generated, even if there are changes in the CSS files, but no new CSS file.
Reproduction
System Info
Output of
npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers
:Used package manager: npm
Before submitting the issue, please make sure you do the following
The text was updated successfully, but these errors were encountered: