The Mix manifest does not exist when it does exist

☆樱花仙子☆ 提交于 2019-12-02 20:37:01

i solved my problem running this command

npm install

and then

npm run production

Thank You.

I had same exception after deployment laravel project to server. It was working perfectly fine on localhost but after lot of research I found a solution. If you encounter this exception on server then you have to bind your public path to public_html

Just go to under the app/Providers, you will find your AppServiceProvider file and inside boot() method make the binding as below.

   $this->app->bind('path.public', function() {
        return base_path().'/../public_html';
    });

The problem I faced was that the mix()-helper function by default looks for the manifest-json file in /public/manifest-json.js so if you store that file on any other directory level then it will throw that error.

Let's say the manifest-json file is stored in public/app/manifest-json.js, then for a file located in public/app/css/app.css you would use:

<link rel="stylesheet" href="{{ mix('css/app.css', 'app') }}">

The mix()-helper function allows for a second argument, the directory of the manifest file. Just specify it there and it will use the correct manifest file.

Solivan

In shared hosts and laravel 5.6 tested: after doing standard levels such as explained here; two levels needed: in app/Providers/AppServiceProvider.php:

$this->app->bind('path.public', function() {
    return realpath(base_path().'/../public_html');
});

and in public_html file make .htaccess file with content:

<IfModule mod_rewrite.c>
  RewriteEngine On
  RewriteBase /
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteRule ^(.*)$ index.php?/$1 [L]
</IfModule>
<IfModule !mod_rewrite.c>
  ErrorDocument 404 /index.php
</IfModule>

source: here this file most change for some situations.

that's all and solved my problem

i have same problem as questioner: manifest does not exist for solving it what i have done is ran 2 commands as following:

npm install

and then

npm run dev

and the error is solved now. yippi.

I had the same issue with a Laravel package, its assets were not published:

This solved the issue for me:

php artisan vendor:publish --tag=telescope-assets --force

Sources: https://github.com/laravel/telescope/issues/136 https://github.com/laravel/telescope/issues/250

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!