Assets linking during the package development

[Nks]

Package

Panel builder

Package Version

v3.2.132

How can we help you?

While actively developing the package, to avoid having to publish styles and javascript every time it changes and see the changes on the fly at the moment, I use symbolic links.

ln -s /app/vendor/package-vendor/package-name/resources/dist/package-name.css /app/public/css/package-vendor/package-name/package-name.css
ln -s /app/vendor/package-vendor/package-name/resources/dist/package-name.js /app/public/js/package-vendor/package-name/package-name.js

Once the package development is complete, these symbolic links will be removed, and the styles will be published via php artisan filament:assets, but maybe there is some other approach that I am not aware of during package development. For example in laravel nova all static package files are handled through the Nova controller itself. Yes, for production and with a large number of users this is not an ideal solution and I would prefer to publish static files as it happens in filament for production environment, but during development when you need to change javascript and css frequently it is very useful.

Is there any similar approach in filament for package development that I missed?