Make Yarn the default, drop default vendor/asset directories #27300
Conversation
|
FWIW we had some issues with yarn at Shopify where they shipped a few fully broken releases and pulled production versions in the last couple weeks. We had to pin the version at 0.16 and are carefully testing the newest one to make sure it doesn't break on us before rolling it out to all developers. 0.17 perhaps was just an anomaly, but it might make sense to wait a month or two to let it stabilize a bit before endorsing it for the whole Rails community. Waiting two more months will double the time it's been in the wild and it doesn't seem like there is much urgency. |
|
@airhorns I think we will have plenty time to test this between now and the first betas of Rails 5.1, I don't think we have a ETA for 5.1 beta yet but I'm pretty sure it won't be released in the next 3 or 4 months. |
|
if configuration bit could be in rails app config itself and assets precompile could indirectly run yarn that would be great |
|
Why is it |
|
👏 |
Yarn is now a part of the Rails default stack. We should use this package manager for our front-end assets like Bootstrap, jQuery, etc. This is a first step, all new js/css libraries should be added via Yarn. https://yarnpkg.com/en/ rails/rails#27300 http://weblog.rubyonrails.org/2016/12/10/this-week-in-rails-yarn-webpack-bigint-pks-and-more/ http://nithinbekal.com/posts/yarn-rails/ [#147836807] Story - https://www.pivotaltracker.com/story/show/147836807
Yarn is now a part of the Rails default stack. We should use this package manager for our front-end assets like Bootstrap, jQuery, etc. This is a first step, all new js/css libraries should be added via Yarn. https://yarnpkg.com/en/ rails/rails#27300 http://weblog.rubyonrails.org/2016/12/10/this-week-in-rails-yarn-webpack-bigint-pks-and-more/ http://nithinbekal.com/posts/yarn-rails/ [#147836807] Story - https://www.pivotaltracker.com/story/show/147836807
Yarn is good. Yarn works.