-
Notifications
You must be signed in to change notification settings - Fork 81
NOTICE: No Longer Maintained #90
Comments
Hi, I was guessing this would be inevitable! Do you have any good resources for migrating to webpacker? Been meaning to do it, but not sure where to start. Thanks for this gem, it really got me up and running with some requirements for a project. |
For us it let us us react_rails & server side rendering :) |
@mipearson would like to take over and keep this project running because we do use it alot |
@iamcaleberic Hi Eric - I'm hoping to pass it on to one of the organisations or people that have previously contributed pull requests. |
@mipearson understood will fork and keep it alive on my end. I am having alot of problems with webpacker particularly with production compilation which this gem handles awesomely so I will keep this running. Thanks for Such awesome work. |
Thanks for your compliments, but I'd give webpacker another go as well. I should really get a writeup together of how we migrated from webpack-rails to webpacker. |
Have you by any chance written that writeup up? :) |
Oh I want the migration guide too haha |
So the trouble is it was somebody else in our team that did the migration .. and it was a while ago! I'll see what I can do. |
@mipearson you can probably create a similar doc, so everyone can contribute – https://github.com/thoughtbot/paperclip/blob/master/MIGRATING.md. |
Hi!
I am no longer maintaining webpack-rails. webpack-rails was created to solve a specific problem we had a Marketplacer - at the time, it was the only way to get webpack working on Rails without either relying on sprockets for asset tagging or following a very long list of instructions.
We've since moved to using https://github.com/rails/webpacker in conjunction with react-rails.
If you have an interest in taking over this project please let me know.
The text was updated successfully, but these errors were encountered: