Closed Sebastiangperez closed 2 years ago
timacdonald
commented
2 years ago You may need to specify the publicDirectory configuration option in your Laravel Vite plugin config.
However, keep in mind that Laravel doesn't support changing the public path.
Sebastiangperez
commented
2 years ago Sorry , but is not working , i tried to do this , but keeps pointing /Laravel/../public/build/manifest.json where laravel is the framework folder and the public is where the index.php and all other files are. Laravel and Public folder are in the same level. i change the name "build" folder for "assets" and all files are in /public/assets/ and there is the manifest.json.
About changing public path , worked for me and for many other projects that i did , also the storage link command maybe do not work but you can simply try to do an ln command and that's it.
Sebastiangperez
commented
2 years ago I don't wanna say anything but i did it .. it worked ..
Description:
I came across with an issue where i need to separate all laravel core framework except public folder and his files , i made a directory same level a public called laravel, all files are in there. i have my public folder , in this case , public_html , with all php files that came in the public laravel folder . I made the changes so i can use the public folder as my document root. the problem is that when i run , npm vite o npm vite build , and use the @vite directive , Vite manifest is not found , seems that is not possible to look up one level up like this : Laravel <- laravel framework Public <- public files from laravel framework
Steps To Reproduce:
Download the laravel framework , install all dependencies, split laravel framework and public folder in separates directories and try to compile or run the build command also using the vite directive.