community-forum icon indicating copy to clipboard operation
community-forum copied to clipboard

Assets should be published to public/vendor instead of public/packages

Open ziming opened this issue 3 years ago • 1 comments
trafficstars

Recently I ran the free Vite Converter on Laravel Shift, and it modifies a lot of published backpack js assets which it should not do.

I later learn that Laravel Shift ignores the public/vendor folder, I also notice other popular or official laravel packages publish assets to public/vendor (e.g. public/vendor/horizon) too so perhaps we should do the same by publishing to public/vendor/backpack for example. To be consistent with them and also for better compatibility with laravel shift.

ziming avatar Jul 09 '22 13:07 ziming

Ugh that's unfortunate. We used to have them in public/vendor, we moved them to public/packages in... v5 I think.

We can only do this in a new major version, so let's consider this when we finish v6. Ideally by then we'd also finish #2682 so there are no/few assets to publish anyway.

Thanks @ziming !

tabacitu avatar Jul 11 '22 07:07 tabacitu

We don't have published files anymore. 🤷

pxpm avatar Sep 19 '24 14:09 pxpm