Laravel breeze installation issue

Level 75

Did you point to public as document root?

Level 1

@jlrdw

yes public folder on root and it is not creating the build folder and files inside it

Level 50

Show the exact commands you ran when you tried to install breeze.

Level 1

@JussiMannisto

I just ran the following commands available on laravel official website

composer require laravel/breeze --dev
php artisan breeze:install
php artisan migrate
npm install
npm run dev

Actually public folder is not crating the build folder and file inisde it

Level 50

@sahiraltaf Those steps are correct.

Actually public folder is not crating the build folder and file inisde it

You don't need a build directory during development.

When you run npm run dev, it starts the Vite development server which enables hot module replacement (HMR). That means any changes you make to the front end code are immediately pushed to the browser without needing a page refresh.

You need to run both the Vite server and a regular web server:

Run npm run dev and don't close the window.
Run your web server, e.g. php artisan serve in another terminal or Apache through XAMPP.

Now you should be able to access your app in a browser.

You only compile the build directory for production. You do that by running npm run build. But you don't need that during development.

Level 1

@JussiMannisto

Yes I am following the same steps

but when I run the command

npm run dev

dev vite

it does not move further

I also have run the regular server

php artisan serve that the running fine

when it hit the URL "http://127.0.0.1:8000/register"

it throws errer:

Illuminate\Foundation\ViteManifestNotFoundException Vite manifest not found at: C:\xampp\htdocs\Roles\public\build/manifest.json

Level 50

You get that error because the Vite server isn't starting up correctly.

Did you get any errors when you ran npm install? If you're not sure, you can try deleting the node_modules directory and running npm install again.

What's your npm version (npm -v)?

And just to be absolutely sure - when you ran npm run dev and it seemingly froze, did you try accessing the site at that point, without exiting the command? That process is supposed to remain in a waiting state. There should be some other text on the screen, but I've never used it on Windows (other than through WSL), so I don't know how it behaves there.

You can also try running npm run build to see if the building process works. But you really want to get Vite working. Otherwise you'd have to re-build the assets every time you make a change.

Level 1

@JussiMannisto

I'm sure, I don't face any error when in run "npm install" command'

npm -v = 10.8.2

I just have run the "npm run dev" command and it seemingly froze and don't build the build folder and its file in public folder. The application runs but throws error on register and login routes.

Illuminate\Foundation\ViteManifestNotFoundException Vite manifest not found at: C:\xampp\htdocs\RolesPersmissions\public\build/manifest.json

Here is vite.config.js File C:\xampp\htdocs\RolesPersmissions\vite.config.js import { defineConfig } from 'vite'; import laravel from 'laravel-vite-plugin';

export default defineConfig({ plugins: [ laravel({ input: [ 'resources/css/app.css', 'resources/js/app.js', ], refresh: true, }), ], });

Here is package.json File C:\xampp\htdocs\RolesPersmissions\package.json

{ "private": true, "type": "module", "scripts": { "dev": "vite", "build": "vite build" }, "devDependencies": { "@tailwindcss/forms": "^0.5.2", "alpinejs": "^3.4.2", "autoprefixer": "^10.4.2", "axios": "^1.7.4", "laravel-vite-plugin": "^1.0", "postcss": "^8.4.31", "tailwindcss": "^3.1.0", "vite": "^5.0" } }

Level 50

@sahiraltaf

I just have run the "npm run dev" command and it seemingly froze and don't build the build folder and its file in public folder. The application runs but throws error on register and login routes.

Again, the missing build directory isn't an issue. It shouldn't exist. But when npm run dev is running, Vite should create a hotfile at public/hot. That file should get deleted when you exit the command.

Your app is trying to read the Vite manifest from the build directory because the hotfile doesn't exist. That should only happen in production, not during development.

You've talked about php artisan serve and XAMPP. Those two use different web servers and can't be used together. You could try turning off XAMPP, Herd, or any other server software that might conflict with artisan serve. Then try starting npm run dev in one terminal, php artisan serve in another, leave them both running, and access the website at http://localhost:8000.

You could also try running npm run build and see if it throws any errors. That creates the build folder but it doesn't fix the real issue with Vite.

Level 1

@JussiMannisto Would you pleasae send me your whatsapp

so i can share video recording what actually happens when i run the command "npm run dev"

Level 50

@sahiraltaf You already described what happens.

You can easily see if the command works or not. Run it in one terminal and leave it running. Then check in another terminal if the file public/hot exists. If it does, the command works.

But you should check if that file exists before you run npm run dev and delete it if it does.

Did you try any of the other stuff I suggested?