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?

Christopher Gilroy 6 days ago

Laravel PHP

3 Answers

Text formatting options

Private reply Submit

Here's a how to add some HTML formatting to your comment:

<pre></pre> for JS codes block
<pre lang="html"></pre> for HTML code block
<pre lang="scss"></pre> for SCSS code block
<pre lang="php"></pre> for PHP code block
<code></code> for single line of code
<strong></strong> to make things bold
<em></em> to emphasize
<ul><li></li></ul> to make list
<ol><li></li></ol> to make ordered list
<h3></h3> to make headings
<a></a> for links
<img> to paste in an image
<blockquote></blockquote> to quote somebody
:)
:|
:(

Replies (3)

Faizal Author 1 day ago

Hi

Yes, this avoids build complexity. If you want a full Vite compilation with Metronic source files, we will consider adding it soon.

Thanks

Gerald 4 days ago

If the goal is faster builds or avoiding extra config, this approach works, but it might create inconsistencies between local development and production.

Christopher Gilroy 3 days ago

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".

Metronic

Go to Metronic Downloads License Guide & FAQ Purchase Metronic I have a Custom Project Refunds

Laravel/Vite integration... why are you using public/assets?

Replies (3)

Metronic

Products

Legal

Stay Connected