Loca Installation does not work right on windows 11

I followed the steps in installation section on the official akaunting repo. The minute I hit php artisan serve and go to localhost:8000 I see this in my console :
10Refused to apply style from '' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
login:1 Uncaught (in promise) TypeError: Failed to register a ServiceWorker for scope ('http://localhost:8000/') with script ('http://localhost:8000/serviceworker.js'): A bad HTTP response code (400) was received when fetching the script.
manifest.json:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
login:1 Manifest fetch from http://localhost:8000/manifest.json failed, code 400
manifest.json:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
login:1 Refused to execute script from 'http://localhost:8000/auth/login' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled. I've done the same thing like 15 times something I'm missing I'm not sure.

Please help

Hi Athreya,

Those errors mean the front-end assets were never built — the CSS/JS files
are not in the repo (public/js and public/mix-manifest.json are gitignored),
so the browser gets HTML 404 pages instead of .css/.js files.

After cloning, the asset build step is required:

npm install
npm run dev (or: npm run prod)

Then:

php artisan storage:link
php artisan cache:clear
php artisan config:clear

On Windows 11, storage:link creates a symlink — run your terminal as
Administrator (or enable Developer Mode), otherwise public/storage is not
created and logos/uploads stay broken.

Also make sure APP_URL in .env matches exactly what you open in the browser:

APP_URL=http://localhost:8000

The manifest.json / serviceworker.js errors are harmless — those files are
only generated on a full install, PWA is simply not active in dev.

If it still fails after npm run dev, please share the output of that command.

I had a similar issue with a Laravel app running locally on Windows. The MIME errors can be misleading because the browser may be receiving an HTML error page where it expects a CSS or JavaScript file. I’d check that the frontend dependencies have been installed and that the assets were actually built before troubleshooting the browser errors.

I’d also check the values, especially , and clear the Laravel config/cache after making changes. If the main page loads but the static files still return 400, checking the Network tab for the first failed CSS or JS request should help pinpoint the problem.