Question 56365 in cPanel Question posted in
The official documentation can be seen here.

Vite manifest not found – CPanel

I Working on project that working with laravel 9 and Vite with laravel-vite,

In Dev environment all thing working fine, but in production cPanel server I has this issue

Vite manifest not found at: /home/???????/cart_shop/public/build/manifest.json

# With 

Missing Vite Manifest File
Did you forget to run `npm install && npm run dev`?

I tried to solve the problem but nothing work, I need to change the public folder and the sup folder build file place from vite.config.js but I don’t find the way to do that.

Note that: the file sequence is changed in cPanel shared server from

- home
    - public_html
        - cart_shop
           - Root
           - public
           - etc

To

- home
    - public_html
       - public files and folders  // I changed the index URLs too.
- cart_shop
    - Root
    - etc

my vite.config.js config is like:

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

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

11

Answers


  1. Chosen as BEST ANSWER
    0

    The issue solved,

    first: I try adding publicDirectory configration into laravel-vite-plugin setting in vite.config.js that solve the build issue but manifest still not founded.

    Finally: I move all files and folders except build from public to bublic_html then npm run build and it's working fine.


  2. 0

    just go to your public folder and there is a hot file in that file there is a link like this http://127.0.0.1:3000 change this link to your domain link i mean your website link

    Login or Signup to reply.
  3. 0

    I had the same issue only because of node version. I upgraded to the latest version and it’s working properly.

    For Ubuntu use n module from npm in order to upgrade node:

    sudo npm cache clean -f
sudo npm install -g n
sudo n stable

    To upgrade to latest version (and not current stable) version, you can use:

    sudo n latest

    You may need also to Fix PATH:

      sudo apt-get install --reinstall nodejs-legacy     # fix /usr/bin/node

    To undo:

      sudo n rm 6.0.0     # replace number with version of Node that was installed
  sudo npm uninstall -g n

    You may need to restart your terminal to see the updated node version.

    Found in Ask Ubuntu

    Login or Signup to reply.
  4. 0

    If the manifest.json file does exist but you’re still seeing this error, make sure the permissions are good:

    sudo chown www-data:www-data -R public/build/
sudo chmod g+w -R public/build/
    Login or Signup to reply.
  5. 0

    I had a similar problem and I was able to resolve it by installing the node current stable version. In my case, the node version was 14+, and when I upgraded to the current version which is v16.17.0, everything works just fine. The comments here were helpful.

    Visit the official node website to download and install the latest node version.

    Login or Signup to reply.
  6. 0

    Type this it’s works for me

    npm run build
    Login or Signup to reply.
  7. 0

    In my case, I have solved this problem by doing some things.

    First of all, I have made sure required npm packages are installed by running this command

    npm install

    After that, I have run

    npm run build

    To build assets and create the manifest file.

    Login or Signup to reply.
  8. 0

    Update Node.js to its latest version: https://nodejs.org/en/

    Then run npm run dev.

    Login or Signup to reply.
  9. 0

    Remove @vite(['resources/sass/app.scss', 'resources/js/app.js']) from the <head> of the file app.blade.php on Laravel 9. And now it works like a charm.

    Login or Signup to reply.
  10. 0

    I solved this problem like this:

    1. npm run build
    2. When you put public files inside public_html. Create a public file in the root of the domain and put the build folder inside it And it was done.
    Login or Signup to reply.
  11. 0

    What fixed it for me was to use a recent version of Node.

    You can use nvm for that:

    nvm use 19
npm run dev
    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search