Thanks @thinkverse! Bit short on time now but will give this a go soon.

I can't get the CSS to render. I keep on running into this with every project I migrate to Vite. Do you know what I need to do here?

Screenshot 2022年09月07日 at 14 28 00

I can't get the CSS to render

I've never had issues running npm run dev or npm run build and loading Vite assets with Valet or artisan serve. Are you using Sail or Docker? Could be that the port for Vite's dev server isn't open if it runs dev? 🤔

Just artisan serve.

I just run the npm scripts in another terminal, I never had issues with that before. Is it a CORS issue, or does the browser block assets from different origins?

How I run Paste with artisan serve ¹ .

@driesvints Looking at it again though, it seems the @vite directive isn't being interpreted by the Blade compiler since it prints out @vite([...]). Did you run composer install to install the updated dependencies?

I'm sure I updated both Composer files to require a version of Laravel where the Vite directive exists.

Yeah, I updated composer.json to use "laravel/framework": "^9.19", which is where the Vite directive was added¹ . And composer.lock was updated using composer update --lock and that locked Laravel to the compatible version v9.27.0. 🤔

It suddenly works for me 🤷‍♂️

Anyway, very much appreciated @thinkverse, thank you!

It suddenly works for me 🤷‍♂️

Computer magic. 🧙‍♂️

I now have issues deploying this... can't figure out what's wrong...

> @ build /home/forge/paste.laravel.io/releases/20220908071709
> vite build
sh: 1: vite: not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! @ build: `vite build`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the @ build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/forge/.npm/_logs/2022-09-08T07_17_32_919Z-debug.log

Seems like vite itself was missing as a dependency. No idea how I ever got it to build locally 😅

How the heck did I miss that? 🤦‍♂️ I don't have Vite installed globally so I wonder how I also got it to build locally. That's a new one. 😂 Good catch. 👍

You know what. I've cracked it, laravel-vite-plugin has Vite as a development dependency so it'll be installed locally, but if you install for production those won't be installed, and since I forgot to add Vite as a dependency it was missing on the server and not locally. 🙂

Thanks for checking that 👍