Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modern asset handling #272

Open
anderscarling opened this issue May 3, 2022 · 0 comments
Open

Modern asset handling #272

anderscarling opened this issue May 3, 2022 · 0 comments

Comments

@anderscarling
Copy link
Collaborator

Asset handling in godmin is really old, mostly using the pre-rails-5.1 (see #222) method of pulling in javascript and css through gems.

This method makes it somewhat hard to isolate the versions of dependencies used by godmin from those of the main app (if both uses gems for assets), even though godmin most likely uses a separate .css and .js file. In some cases it also has us stuck on old versions of some dependencies.

This old tech stack can also interfere with users desire to run a more modern stack (see brunoprietog's comments in #265.)

It would be great to find a way to modernise the asset handling in a fashion that allows us to pull in the latest versions of dependencies through yarn/npm - but also isolate the way assets are handled in godmin from what our host application will be using. Maybe we should just ship complied and minimised css and js with the gem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant