Tim MacDonald
Tim MacDonald
@dammy001, that value is already being flushed 🤙
I'm wondering if we need to consider how this ties in with https://github.com/laravel/vite-plugin/pull/251 to give a holistic framework approach - or at least a consistent naming convention.
I love this idea. My concern is that the implementation will lead to issues during deployments. Imagine you have a package that has published `public/vendor/acme/scripts.abc123.js`. You update the underlying package...
@gdebrauwer it was awesome getting to hang with you! I'm think more when you wouldn't have these committed to your git repository and instead publish them as part of your...
I agree this is a good command! We could use it in Forge. Just wanna make sure it supports my concerns outlined. I plan to come back and get this...
I've hit a similar issue in the past where there was a directive defined in the Laravel app that matched one of Tailwinds `@` things, e.g, an `@container` blade directive...
Thanks. Appreciate the reviews.
@Girgias, no apologies needed! I've just rebased against master here and re-checked the repository in case others had been introduced. This should be good to go.
Thanks, Pat 👋
Context: In Vite 4, the dev server works with and without the `/frontend` prefix. In Vite 5 is breaks.