Monday, October 14, 2019
On Monday, October 14, 2019 at 6:50:53 PM UTC-4, Ariel Juodziukynas wrote:
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 behaviourEl lun., 14 oct. 2019 19:44, fugee ohu <fuge...@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 rubyonra...@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
When I run yarn install it doesn't create a /public/packs folder and that's the cause of my
Webpacker::Manifest::MissingEntryError error? Because the manifest file isn't found?
Webpacker::Manifest::MissingEntryError error? Because the manifest file isn't found?
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/da0ad727-e0d7-4796-ba49-2c5fbe4a68c6%40googlegroups.com.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment