# Troubleshooting

Here are solutions to common problems encountered with either Vite or Laravel Vite. If you encounter an issue that is not mentionned here, feel free to open a discussion.

# The manifest could not be found

This means that Laravel Vite is trying to use a manifest file instead of communicating directly with the development server. This could happen in development if your environment is not set up correctly.

# In development

• Make sure APP_ENV is set to local.
• Make sure you started the development server with vite (npm run dev).
• Depending on your local environment, you may want to set ping_timeout to false in config/vite.php to disable the automatic development server discovery.

# In production

• Make sure you generated the manifest with vite build (npm run build).
• Make sure the manifest has been generated in build_path.

# Local https doesn't work

Setting up https locally requires a few settings. The development server must use https if your application uses it in order to make HMR work, because the websocket will use the wss protocol, which needs a secure context.

• Ensure Vite knows about your SSL certificates (see withCertificates).
• Ensure dev_url in config/vite.php is using the https protocol.
• Manually visit https://localhost:3000 (or whatever your dev_url is set to) in your browser to approve the self-signed certificate.

# The page is refreshing in a loop

This is due to the client's websocket not being able to connect to the development server, most likely because of improperly configured SSL. See Local https doesn't work.

# Imported assets don't load in the local environment

Make sure you are using Vite v2.6.0+.

Before that, there was a known issue caused by Vite stripping the hostname of the base URL when developping locally. A way around this issue was to use a fallback route to redirect to the right URL:

// AppServiceProvider.php
public function register()
{
    Vite::redirectAssets();
}

This method simply registers the following route when the environment is set to local:

// Workaround for https://github.com/vitejs/vite/issues/2196
Route::get('/resources/{path}', function (string $path) {
    if (! App::environment('local')) {
        throw new NotFoundHttpException();
    }

    return Redirect::to(config('vite.dev_url') . '/resources/' . $path);
})->where('path', '.*');

This method is deprecated and will be removed in a future version.

# How do I get the path of a Vite -rocessed asset from the back-end?

There is currently no way to get the path of a Vite-processed asset (eg. an image that was imported in a Vue SFC) from the back-end, since the manifest does not reference the original file path. In most cases, this should not be an issue, as this is not a common use case.