Level 102
Show how you are adding it in your blade code along with your vite config
Oct 19, 2022
10
Level 3
Vite CSS file not found in production - Cached Manifest?
I have just started using Vite on a recent project. I am building the CSS files locally and pushing them to git. Envoyer is just deploying all files and not building anything.
Everything works fine locally and my first production deployment worked also.
Subsequent production deployments through Envoyer are failing to find my CSS file, with a 404 error.
I checked the production deployed manifest file and CSS files and they all match up, however my app is looking for an old CSS file that was previously deployed.
I have tried all the cache:clear config:clear view:clear commands but nothing is working.
Production Manifest:
{
"resources/js/app.js": {
"file": "assets/app.ab93cf8a.js",
"src": "resources/js/app.js",
"isEntry": true
},
"resources/css/app.css": {
"file": "assets/app.1ec01807.css",
"src": "resources/css/app.css",
"isEntry": true
}
}
File being looked for by production app:
https://...URL.../build/assets/app.6f1520e8.css
Level 3
I have not updated anything from the fresh L9 install.
So blade:
@vite(['resources/css/app.css', 'resources/js/app.js'])
Vite Config:
import { defineConfig } from 'vite';
import laravel, { refreshPaths } from 'laravel-vite-plugin';
export default defineConfig({
plugins: [
laravel({
input: [
'resources/css/app.css',
'resources/js/app.js',
],
refresh: [
...refreshPaths,
'app/Http/Livewire/**',
],
}),
],
});
Level 102
@booni3 ah ok so you just posted the wrong guide or?
Level 3
@Sinnbeck Yes sorry.
At the moment it works if I set my production ENV to local... but as soon as I switch it back to production the manifest does not seem to be read.
Level 3
If I set my production APP_ENV to "local" then it works again. So this must be something to do with how Vite uses the manifest in Local vs. Production.
I have read the docs but cannot work it out...
Level 102
@booni3 ah. I thought you were using the official plugin
Level 3
Yes sorry I am. I just found that other site too. Assumed it was the same but maybe not. I have read the officail docs too (updated my original message)
Level 2
I'm encountering the same issue. @booni3 Did you ever determine the cause and/or fix? I'm also using Inertia, wondering if that's a factor?
Level 54
@troygilbert I have to reload PHP on the server after every deployment to prevent that issue
Level 3
@troygilbert my issue was a php version mismatch when deploying through envoyer.
Forge default php version and the selected version in envoyer were different.
Please or to participate in this conversation.