Laravel & InertiaJS not compiling

but in my whole repository doesn't exist a index.html file, and it stills compiling 🤔 updating the code, pulling last commits, makes it break

@pmattheew Updating what? And vite does not need an index.html. Maybe show your vite.config.js as a start

@Sinnbeck alright.

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';
import vue from '@vitejs/plugin-vue';

const vitePort = 5173;

/**
 * Checks if any GitPod/Codespaces environment variable
 * is present and returns its Vite port URL; otherwise 
 * returns null.
 *
 * @returns GitPod/Codespaces URL | null
 */
const getCloudEnv = () => {
    const {
        GITPOD_WORKSPACE_URL,
        CODESPACE_NAME,
        GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN,
    } = process.env;
    if (GITPOD_WORKSPACE_URL) {
        return `${vitePort}-${GITPOD_WORKSPACE_URL.substring(
            'https://'.length
        )}`;
    } else if (CODESPACE_NAME) {
        return `${CODESPACE_NAME}-${vitePort}.${GITHUB_CODESPACES_PORT_FORWARDING_DOMAIN}`;
    }
    return null;
};

const server = getCloudEnv()
    ? {
          port: vitePort,
          host: '0.0.0.0',
          hmr: {
              host: getCloudEnv(),
              clientPort: 443,
          },
      }
    : undefined;

export default defineConfig({
    plugins: [
        laravel(['resources/css/app.scss', 'resources/js/app.js']),
        vue({
            template: {
                transformAssetUrls: {
                    base: null,
                    includeAbsolute: false,
                },
            },
        }),
    ],
    server,
});

you can see that I created this getCloudEnv() function because I develop using codespaces/gitpod...

@pmattheew ok. So first thing. Try using the default that comes with laravel. Does that fix it?

@Sinnbeck actually not; I tried commenting the function and the server declaration, also removing the server property of the object... stills throwing 😫

@pmattheew Ok. Then we can rule that out.

And its when comiling locally it fails also I assume?

@Sinnbeck yes, locally it is throwing the same error... Any suggestion where I could look out that could be the cause of this issue? 🤔

@pmattheew personally I would strip it way down. Make the simplest app.js file you can and test. Or make a new project and see if you can compile that. And copy over your resources

@Sinnbeck thank you so much for your help! Today with more calm I could examine it closer following your steps and I could find the reason why it was not compiling.

In this project I had to move my vite.config.js to a new folder, vite/vite.config.js, to store some related scripts within, and when running the vite build command it also asks for the config file, but it wasn't being passed in my npm script. I've configured it for my dev server before with vite -c ./vite/vite.config.js but not for my build command. So doing it solved my issue! Thanks!

@pmattheew Ah exelent. Would have never guessed that :D