You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i think it could benefit activeadmin's popularity to have less dependencies.
with more and more rails apps being API-only, activeadmin is now probably one of the major reasons why people set up sprockets in their apps, which seems a bit wasteful just to compile JS that doesn't usually change.
on the CSS side, installing sassc always used to be a bit of a nuisance with its tricky compilation. the activeadmin v4 way, however, of having to install node + node modules + running a yarn watcher alongside rails, feels like an even bigger burden, especially if this is just to compile some CSS that doesn't usually change, and it does lead to some struggles as seen in #7947, #8223, #8226.
people have come up with hacks to work around this. this blog describes how to use tailwindcss-rails to circumvent the node requirement, restoring roughly the level of "comfort" that sassc used to provide. some people have forked AA with the assets included. others have monkeypatched the asset tag helpers to render CDN URLs instead. what would be ideal, IMHO, was if AA itself were to offer some lightweight and convenient way to render itself ...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
i think it could benefit activeadmin's popularity to have less dependencies.
with more and more rails apps being API-only, activeadmin is now probably one of the major reasons why people set up sprockets in their apps, which seems a bit wasteful just to compile JS that doesn't usually change.
on the CSS side, installing sassc always used to be a bit of a nuisance with its tricky compilation. the activeadmin v4 way, however, of having to install node + node modules + running a yarn watcher alongside rails, feels like an even bigger burden, especially if this is just to compile some CSS that doesn't usually change, and it does lead to some struggles as seen in #7947, #8223, #8226.
people have come up with hacks to work around this. this blog describes how to use tailwindcss-rails to circumvent the node requirement, restoring roughly the level of "comfort" that sassc used to provide. some people have forked AA with the assets included. others have monkeypatched the asset tag helpers to render CDN URLs instead. what would be ideal, IMHO, was if AA itself were to offer some lightweight and convenient way to render itself ...
Beta Was this translation helpful? Give feedback.
All reactions