Monday, October 14, 2019
You shouldn't need to do that, you could use yarn to manage JavaScript dependencies with rails 5 too. Also the assets pipeline still works the same way with rails 6, only webpacker is the default now, but you can keep the old behaviour
El lun., 14 oct. 2019 19:44, fugee ohu <fugee279@gmail.com> escribió:
to upgrade an app to rails 6 i should run `yarn add <requirement>' for everything that was listing as "//= require <requirement>" ?--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c28d3d35-5c90-4228-bdb6-236268bf5f09%40googlegroups.com.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAPS3bcCn_sQgiNia-Xi0eZgGS16Es3t94rBzAkFQaJb20X%2BXPw%40mail.gmail.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment