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

Feature request - webpacker #243

Closed
alec-c4 opened this issue May 17, 2019 · 3 comments
Closed

Feature request - webpacker #243

alec-c4 opened this issue May 17, 2019 · 3 comments

Comments

@alec-c4
Copy link

alec-c4 commented May 17, 2019

Hi,
Do you have plans to add webpacker support? It would be useful because of webpacker becomes the main tool for managing assets for rails applications.

@ankane
Copy link
Owner

ankane commented May 18, 2019

Hey @alec-c4, Rails 6 still includes Sprockets, so it's not needed right now. Blazer assets are completely separate from application assets, so this shouldn't make a difference.

@ankane ankane closed this as completed May 18, 2019
@dzirtusss
Copy link

Just FYI, this is how it is done in ActiveAdmin activeadmin/activeadmin#5855

@jmoore53
Copy link

I was going to comment on this with a question and ask about possible workarounds because I ran into a similar issue, but ended up just adding sprockets & uglifier to my Gemfile, and then setting config.assets.compile=true in config/environments/production.rb

It's a sloppy and noticeably slow workaround to compile assets on the fly in production, but it works for my small production environment because all other assets end up getting compiled via webpacker for the users/public pages and this is behind and admin login/ authn/z.

I'm aware this issue is marked closed, but I wanted to share it out here in case anyone was looking for a workaround.

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

No branches or pull requests

4 participants