Blade @vite directive not detecting public/build Folder

• Laravel Vite Plugin Version: ^0.4.0
• Laravel Version: ^9.19.0
• Node Version: 18.6.0
• NPM Version: 8.13.2
• Host operating system: macOS 10.15.7
• Web Browser & Version: Chrome 104.0.5112.48
• Running in Sail / Docker: No

Description: Running npm run dev works well but when I run npm run build, the build folder is created as expected in public/build but the @vite direction in blade isn’t picking up the build folder at all. It keeps looking for @vite/client even though it is no longer in dev mode.

Steps To Reproduce:

1. Run npm run build after installing all the packages.
2. In the main blade entry file, add @vite(['resources/js/app.js']) (I tried adding the build directory too @vite(['resources/js/app.js'], 'build') and that didn’t work)
3. Visit the site in the browser and it should fail showing an net::ERR_CONNECTION_REFUSED in console.

This is my vite.config.js file:

import { defineConfig } from "vite";
import fs from "fs";
import { homedir } from "os";
import laravel from "laravel-vite-plugin";
import { resolve } from "path";
import vue from "@vitejs/plugin-vue";

let host = "stats.test";
export default defineConfig({
    plugins: [
        laravel("resources/js/app.js"),
        vue({
            template: {
                transformAssetUrls: {
                    base: null,
                    includeAbsolute: false,
                },
            },
        }),
    ],
    resolve: {
        alias: {
            src: resolve(__dirname, "resources/js"),
            modules: resolve(__dirname, "resources/js/components/modules"),
            frontend: resolve(__dirname, "resources/js/components/frontend"),
            vendor: resolve(__dirname, "resources/js/vendor"),
            lang: resolve(__dirname, "resources/languages"),
        },
    },
    server: detectServerConfig(host),
});

function detectServerConfig(host) {
    let keyPath = resolve(homedir(), `.config/valet/Certificates/${host}.key`);
    let certPath = resolve(homedir(), `.config/valet/Certificates/${host}.crt`);

    if (!fs.existsSync(keyPath)) {
        return {};
    }

    if (!fs.existsSync(certPath)) {
        return {};
    }

    return {
        hmr: { host },
        host,
        https: {
            key: fs.readFileSync(keyPath),
            cert: fs.readFileSync(certPath),
        },
    };
}

[timacdonald]

This will happen if the public/hot file still exists.

check that you haven’t accidentally committed this file to the project repository. If it exists, delete it.

The plug-in should automatically delete it when it shuts down the HMR server, but potentially you committed the file while it was running.

If that isn’t the case, let us know.

[haleyngonadi]

@timacdonald It’s in my .gitignore file for sure (from my laravel mix days) but I usually run build locally and push build files to my prod server.