Support Webpack about wallaby-rails HOT 6 CLOSED

I'm not sure if Webpack is supported for a Rails engine, not from what I can see in Rails 5. But yeah, I can take a look and see if it can be done.

from wallaby-rails.

From my understanding there's no way to add node dependencies through a gem so you can't use it through an engine the same way sprockets is used. You can still do it, but the the node dependency needs to be added separately.

For example, let's say you have a wallaby-webpacker gem which is designed to work with webpacker instead of sprockets. To install it you'd do:

gem install wallaby-webpacker
yarn add wallaby-rails # or whatever you name the module

Then they need to generate a pack file:

// in app/javascript/packs/wallaby.js
import 'wallaby-rails'

Then the wallaby layout needs to link to that pack:

<%= stylesheet_pack_tag "wallaby", media: "all" %>
<%= javascript_pack_tag "wallaby" %>

Perhaps supply a generator to do these steps.

Why do we want this? Currently Wallaby depends on these gems: bootstrap, bootstrap4-datetime-picker-rails, jquery-rails, momentjs-rails, sass-rails, font-awesome-sass. These are all front-end dependencies and our app is using the node versions. This duplicates the dependencies of our app for all of these assets, and every deploy generates two copies of these dependencies: one through sprockets and another through webpack.

In theory we could remove sprockets entirely if wallaby didn't use it.

from wallaby-rails.

Yeah, I totally understand why everyone wants it these days. Let me do some experiments and see.

from wallaby-rails.

This is some extra information about how to include assets in engines:
https://github.com/rails/webpacker/blob/master/docs/engines.md

from wallaby-rails.

@leomao10 try this: rails/webpacker#348 (comment)

from wallaby-rails.

Since Webpacker is retired, I suggest not doing what I recommended above. I'm closing this issue.

from wallaby-rails.