Level 50
You're mixing yarn and npm, which seems weird to me. Use npm run dev instead of yarn dev.
The bundler is complaining about not finding resources/admin/sass/admin.scss. Does it exist?
1 like
May 15, 2026
2
Level 5
Can't browse site after clonning git repository
Hello,
Using Laravel 12, I cloned my github repository into c:\wamp64\www
I ran: composer install
composer update
npm install
I copied my .env file from a previous folder I had for this project.
I ran yarn dev, got these errors:
(!) Failed to run dependency scan. Skipping dependency pre-bundling. Error: failed to resolve rollupOptions.input value: "resources/admin/sass/admin.scss". at resolvePath (file:///C:/wamp64/www/mysite.local/node_modules/vite/dist/node/chunks/config.js:31449:29) at async Promise.all (index 2) at async computeEntries (file:///C:/wamp64/www/mysite.local/node_modules/vite at async scan (file:///C:/wamp64/www/mysite.local/node_modules/vite/dist/node/chunks/config.js:31388:19) at async file:///C:/wamp64/www/mysite.local/node_modules/vite/dist/node/chunks/config.js:34131:15
I have the right database credentials and the actual database.
Trying to run the site in the browser, I get this message:
Looks like there’s a problem with this site
Firefox can’t connect to the server at mysite.local What can you do about it?
Try connecting on a different device. Check your modem or router. Disconnect and reconnect to Wi-Fi.
What am I doing wrong please?
Level 5
Jussi is spot on about mixing npm/yarn and the missing SCSS file. Stick to npm run dev since you already built your node_modules with npm install. For that missing admin.scss file, double check your .gitignore it’s very common for custom asset directories to accidentally get ignored, meaning it never actually made it to your Github repo in the first place.
Regarding the "Firefox can't connect" error, that's entirely a local DNS/WAMP issue, not a Laravel bug. Your OS simply doesn't know where to route mysite.local
Please or to participate in this conversation.