Summary
"Vite manifest not found at: /var/www/app/public/build/manifest.json" is the error Laravel throws when a page calls @vite(...) and the compiled assets do not exist on the server. The whole site can return a 500 page, or pages load with no CSS and no JavaScript. It usually appears right after a first deploy, a move to a new server or container, a Laravel 9 to 10 or 11 upgrade (Mix to Vite), or a Git deploy that never ran the front-end build.
This guide gives you the fast isolation steps first. If you would rather hand it over, SazM offers an affordable, low-cost Laravel Vite manifest fix for a fixed $99 price, delivered within 48 hours, entirely in writing: no calls, no project manager, one senior developer.
Where the Error Lives
The @vite Blade directive reads the manifest that vite build writes. If the file is missing, or does not list the entry you asked for, Laravel raises an exception:
Illuminate\Foundation\ViteManifestNotFoundException
Vite manifest not found at: /var/www/app/public/build/manifest.json
Unable to locate file in Vite manifest: resources/css/app.css.
Files worth checking:
public/build/manifest.json # Laravel Vite 5+ may write public/build/.vite/manifest.json
public/hot # leftover dev-server marker, must NOT exist in production
vite.config.js # input entries, laravel-vite-plugin options
resources/views/layouts/*.blade.php # the @vite([...]) call
.gitignore # usually ignores /public/build and /public/hot
.env # APP_ENV, APP_URL, ASSET_URL
storage/logs/laravel.log
Note the second error line: the manifest exists, but the file named in @vite([...]) is not one of the entries it was built from.
Quick Fix Breakdown (DIY)
- Build the assets on the machine that serves them. Because
/public/buildis normally git-ignored, a plaingit pullnever delivers it:
npm ci
npm run build # runs "vite build"
ls -la public/build
- Check the manifest path. Recent
laravel-vite-pluginand Vite versions write the manifest topublic/build/.vite/manifest.json(Vite 5 and later place it in a.vitefolder), and current Laravel releases read from that location. If the build ran but Laravel still says "not found", confirm thatlaravel/frameworkandlaravel-vite-pluginare on matching, up-to-date versions. A mismatch is a common cause after a partial upgrade. - Delete a leftover
public/hotfile. If it exists, Laravel tries to load assets from the dev server instead ofpublic/build:
rm -f public/hot
- Make the entries match. Every path in
@vite(['resources/css/app.css', 'resources/js/app.js'])must also appear ininputinvite.config.js. Rebuild after any change. Extra view-specific entries (for exampleresources/js/admin.js) need to be listed too. - Install dev dependencies in CI.
npm ci --omit=devremoves Vite itself, sonpm run buildfails. Build in a stage that has dev dependencies, then ship onlypublic/build. - Check Node and file permissions. Use a Node version that your Vite release supports, and confirm the web user can read the folder:
node -v
ls -ld public public/build
- Clear caches after changing
.envor views:
php artisan optimize:clear
php artisan view:clear
- Containers and multi-server setups. Build assets into the image (a Node build stage) or run the build in the pipeline, and publish the same
public/buildto every server. If you use a CDN, setASSET_URLcorrectly and purge the old files. - Do not "fix" it by committing
node_modulesor by switchingAPP_ENVtolocal. Hiding the exception does not give you working, hashed production assets.
If none of these isolates it within an hour, stop. Every extra hour is a broken storefront or admin panel.
Hand It Over: $99 Fixed, Within 48 Hours
This error looks like one missing file, but the cause sits in the build step, the deploy script or the container, and a wrong guess just moves the failure. One developer who checks the pipeline, the Vite config and the server together ends the guessing.
What you get for $99:
- A fixed price agreed before work starts. One issue, one flat fee, no hourly meter.
- Delivery within 48 hours of access, with the fix verified on staging before anything touches production.
- Fully written, fully async. You send the URL, the exact error, how you deploy (Git pull, CI, Docker, a host panel) and what changed recently. You get questions, progress and proof in writing. There are no calls, meetings or project managers.
- Written proof it works: the root cause in plain language, which files or settings changed, a before and after check, and a rollback note.
- Money-back guarantee if the agreed root cause cannot be resolved.
- Safe access only: a limited SSH, hosting or repository account that you can revoke. Never send passwords through the inquiry form.
If the page loads but a form then fails with "419 | Page Expired", see Laravel 419 Page Expired fix. If the whole app returns a generic "Server Error" instead, see Laravel 500 error fix.
Behind it: 20+ years in production (since Oct 2006) and 100+ projects in the portfolio.
Get this error fixed for $99 → · Queue an urgent fix · See past projects
For wider application work, see PHP and Laravel development.
Frequently Asked Questions
What does "Vite manifest not found" mean in Laravel?
The @vite directive could not find the manifest file that vite build creates, usually public/build/manifest.json or public/build/.vite/manifest.json. Either the build never ran on the server, its output was not deployed, or a leftover public/hot file points Laravel at a dev server.
Why does it work locally but fail in production?
Locally, npm run dev runs the Vite dev server and creates public/hot, so no built files are needed. In production there is no dev server, so npm run build must run during deploy and public/build must exist on every server.
Should I commit public/build to Git to make the error go away?
It works as a stopgap, but it clutters history and causes merge conflicts. A better fix is to build assets in your deploy pipeline or Docker image so each release ships matching, hashed files.
How much does it cost to fix a Laravel Vite manifest error?
SazM fixes one issue for a fixed $99, delivered within 48 hours, with a money-back guarantee if the agreed root cause cannot be resolved. Typical agency hourly rates are higher and open-ended, while very low marketplace gig prices rarely include root-cause diagnosis, a staging test or a guarantee.
Do I need a call to explain the problem?
No. Send the URL, the error text and how you deploy. A written report is more precise than a call.