Definitely will in the future. In short, Webpack is independent of the asset pipeline. Rails 6 will ship with the webpack support by default. That creates a new javascript directory in the main app folder. There you can wrangle any modern JavaScript.
At the moment the Rails team suggests authoring JavaScript inside the javascript/packs directory and leaving CSS and images/assets for the asset pipeline to deal with.
/developer|entrepreneur/i
Always looking for new developer talent, even those with zero experience, as you never know who's got the potential to become a great developer.
Disabling Ruby's asset pipeline and swapping in Webpacker as the exclusive method of packing assets is annoying, but often necessary. Even DHH has admitted that ye-olde asset pipeline is coming to an end soon and that Webpacker is the future.
I've appreciated what the asset pipeline has done for me in the past, but it just isn't as configurable as things like Webpack.
A walkthrough for Rails 6 would be a great resource to have.
I love web development and it's my principal hobby and my planner to transition career. So I'm dedicating my time learn RubyOnRails and using Docker, Git/Github and Postgres...
Yes Scott, in this moment I'm use pipeline in my current project only to images and stylesheets. For javascript I'm using webpack yet. I'm thinking a bit slowly to compile the assets but it's my first tests...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Definitely will in the future. In short, Webpack is independent of the asset pipeline. Rails 6 will ship with the webpack support by default. That creates a new
javascriptdirectory in the mainappfolder. There you can wrangle any modern JavaScript.At the moment the Rails team suggests authoring JavaScript inside the
javascript/packsdirectory and leavingCSSand images/assets for the asset pipeline to deal with.I'll have walkthrough of this soon
Disabling Ruby's asset pipeline and swapping in Webpacker as the exclusive method of packing assets is annoying, but often necessary. Even DHH has admitted that ye-olde asset pipeline is coming to an end soon and that Webpacker is the future.
I've appreciated what the asset pipeline has done for me in the past, but it just isn't as configurable as things like Webpack.
A walkthrough for Rails 6 would be a great resource to have.
Yes Scott, in this moment I'm use pipeline in my current project only to images and stylesheets. For javascript I'm using webpack yet. I'm thinking a bit slowly to compile the assets but it's my first tests...