Add single files to assets compilation

[morgoth]

Looking at https://github.com/rails/cssbundling-rails/pull/147/files It's a nice way to pin javascript files from node packages.

However this example includes all the files that are placed in given directory, ie

Rails.application.config.assets.paths << Rails.root.join("node_modules/bootstrap/dist/js")
will output on rails assets:reveal:

...
bootstrap.min.js.map
bootstrap.esm.js.map
bootstrap.bundle.js
bootstrap.esm.js
bootstrap.js
bootstrap.min.js
bootstrap.bundle.min.js
bootstrap.bundle.min.js.map
bootstrap.bundle.js.map
bootstrap.js.map
bootstrap.esm.min.js
bootstrap.esm.min.js.map
...

So all those files will be digested and put in public path.
Looks like it's not possible to pick only one file or exclude any others from digesting as the config.assets.excluded_paths and config.assets.paths takes directories only.

Is there any way to achieve this?

It's softly connected to https://github.com/rails/propshaft/issues/89`

@brenogazzola did you have a chance to look at paths handling, vide #89 (comment) ?

[brenogazzola]

We discussed a few options and David said he'd think about it and come up with something himself. I'll ping him about it.

[mjansing]

Any updates on this? I'm also interested in a solution.

[brendon]

This definitely needs a solution. With Sprockets we could add node_modules to assets.paths and pull whatever particular files we want. Now Propshaft digests every single file which just isn't performant on a large project. I suspect there needs to be a seperate configuration option for search paths over digest paths.

[mzedeler]

@brenogazzola - any news on this? I have the exact same issue and I wonder how others deal with this. Do you have some suggested workarounds?

[brendon]

I ended up adding specific node_modules directories in assets.rb:

Rails.application.config.assets.paths << Rails.root.join("node_modules/froala-editor")

Then I could do a sketchy @use like so in my scss file:

@use 'css/froala_style';

It's sketchy because I guess depending on the structure of the particular project one could easily have naming collisions. In my case it worked out ok.

Still needs a proper solution though I think.