Laravel/Vite integration... why are you using public/assets?
I swore a few versions ago your Laravel integration properly configured Vite and tailwind.config.js?
Now it looks like you're just putting everything pre-compiled into public/assets?
Replies (4)
Laravel’s Vite integration isn’t about “going back” to public assets, it’s about shipping predictable, cacheable files that the browser can actually reach. At the end of the day, the URL is what matters—just like a music app where must resolve cleanly, your compiled CSS and JS must live at a stable, public URL. Vite builds fast, versioned assets, and Laravel serves them from `public` because that’s the contract of the web: anything the browser needs must be publicly accessible, optimized, and cache-friendly. Hiding assets doesn’t make an app( veduhd.app/vedu-for-ios/ ) more modern; clean URLs and reliable delivery do.
Hi
Yes, this avoids build complexity. If you want a full Vite compilation with Metronic source files, we will consider adding it soon.
Thanks
If the goal is faster builds or avoiding extra config, this approach works, but it might create inconsistencies between local development and production.
That's basically my point, it seems like with v9.2+ and Tailwind v4 they threw their hands up (even in the docs) and just said "meh, only use the precompiled styles and scripts".
