Vite Cannot be configured safely from a layout file #58704

dadaxr · 2026-02-03T12:18:28Z

dadaxr
Feb 3, 2026

Laravel Version

12.49

PHP Version

8.4.13

Database Driver & Version

No response

Description

According to the doc https://laravel.com/docs/12.x/vite#advanced-customization

we can configure Vite directly from a layout file :

<!doctype html>
<head>
    {{-- ... --}}
 
    {{
        Vite::useHotFile(storage_path('vite.hot')) // Customize the "hot" file...
            ->useBuildDirectory('bundle') // Customize the build directory...
            ->useManifestFilename('assets.json') // Customize the manifest filename...
            ->withEntryPoints(['resources/js/app.js']) // Specify the entry points...
            ->createAssetPathsUsing(function (string $path, ?bool $secure) { // Customize the backend path generation for built assets...
                return "https://cdn.example.com/{$path}";
            })
    }}
</head>

But actually, when rendering a blade page which use a layout (either throught @extend directive or blade component), the page blade content is "proccessed" before the content in the layout file ...

So ... for instance if set a custom HotFile, in the layout, and use a {{ Vite::asset('resources/images/whatever.svg') }} in the blade file... It will fail because the later is called sooner...

The workaround is to set custom Vite options in a ServiceProvider ... But to me, the doc is misleading.

Steps To Reproduce

Configure Custom Vite Options in a layout file ie :

<!doctype html>
<html>
<head>
    {{
        Vite::useManifestFilename('custom-manifest.json') // Customize the manifest filename...
            ->withEntryPoints(['resources/js/app.js','resources/css/site.css']) // Specify the entry points...
    }}
</head>
<body>
@yield('main_content')
</body>
<html>

And in a blade view file :

@extends('layout')

@section('main_content')
{{ Vite::asset('resources/images/whatever.svg') }} //this crash because the default manifest.json file does not exists, but it should look into the custom-manifest.json file 
@endsection

(optionnaly : In your vite config file, configure the custom-manifest.json)

...
export default defineConfig({
    build: {
        manifest: 'custom-manifest.json',
    },
    ...
...

hugoboss17 · 2026-02-05T12:35:33Z

hugoboss17
Feb 5, 2026

When you use the Vite configuration directly from a Blade file, you should also replicate that configuration on the vite.config.js as the docs say. I see you have the manifest option set but you can send the whole file to compare and try to reproduce?

0 replies

dadaxr · 2026-02-05T13:00:04Z

dadaxr
Feb 5, 2026
Author

Of course, but nothing fancy in my vite.config.js :

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
     build: {
        manifest: 'custom-manifest.json',
    },
    plugins: [
        laravel({
            input: [
                'resources/css/site.css', 'resources/js/app.js',
            ],
            refresh: true,
        }),
    ],
    server: {
        watch: {
            ignored: [
                '**/storage/framework/views/**',
            ],
        },
    },
});

0 replies

hugoboss17 · 2026-02-06T21:06:25Z

hugoboss17
Feb 6, 2026

Ok I just checked this out and the problem is on your resources/js/app.js file.

Just follow the documentation below and everything should be fine, I just tested on my side and it worked.
Processing Static Assets With Vite

0 replies

dadaxr · 2026-02-09T06:09:14Z

dadaxr
Feb 9, 2026
Author

I'm sorry but I dont think so.

I've read & followed the doc.

My app.js does contains this line :

import.meta.glob('../images/**/*', {eager: true})

after running a npm run build

I do have a custom-manifest.json file with my assets :

Custom-manifest.json file does contain the right path :

{
  "resources/images/logo-BSR-192x192.png": {
    "file": "assets/logo-BSR-192x192-FeAXFCJd.png",
    "src": "resources/images/logo-BSR-192x192.png"
  },
  "resources/js/app.js": {
    "file": "assets/app-VYRn_PhH.js",
    "name": "app",
    "src": "resources/js/app.js",
    "isEntry": true,
    "css": [
      "assets/app-C53Xoit_.css"
    ]
  }
}

Once again, after checking the callstack, it seems that the blade content in the main view file, is processed before the one in the layout file, so any custom vite configuration done at the layout level is not yet "known".

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Vite Cannot be configured safely from a layout file #58704

Uh oh!

{{title}}

Uh oh!

Replies: 4 comments

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Vite Cannot be configured safely from a layout file #58704

Uh oh!

dadaxr Feb 3, 2026

Laravel Version

PHP Version

Database Driver & Version

Description

Steps To Reproduce

Replies: 4 comments

Uh oh!

hugoboss17 Feb 5, 2026

Uh oh!

Uh oh!

dadaxr Feb 5, 2026 Author

Uh oh!

hugoboss17 Feb 6, 2026

Uh oh!

dadaxr Feb 9, 2026 Author

dadaxr
Feb 3, 2026

hugoboss17
Feb 5, 2026

dadaxr
Feb 5, 2026
Author

hugoboss17
Feb 6, 2026

dadaxr
Feb 9, 2026
Author