Sprockets ignoring top-level manifests in Rails 5 and Refinery

[bsodmike]

Hi all, @rafaelfranca,

I spent time today troubleshooting an issue in Refinery with Rails 5 and have even shared an example app to demonstrate the issue.

Having discussed this with the author of Refinery, searching vehemently with ag, and looking through as many dependencies I have yet to find a spot within Refinery where it mutates Sprockets.

The behaviour I'm seeing is this:

• New Rails 5 app
• Custom top-level asset manifests are added
• helpers used in layout to render those manifest links into DOM.

Works fine. Once Refinery is added though, the top-level manifests no longer resolve via the Sprockets resolver, but only the assets within refinery-core seem to be handled correctly by Sprockets.

Something is causing sprockets to become seemingly blind to any manifests added to the top-level app — and it doesn't matter that top-level assets do appear in the config.precompile array.

Appreciate any feedback, and thanks again.

References:

• Issue: https://github.com/refinery/refinerycms/issues/3178
• Demo app: https://github.com/bsodmike/refinery-rails-5-sprockets-issue-3178

[bricesanchez]

Friendly ping :)

[bsodmike]

I'd also recommend anyone taking a look to use the check_wymeditor_breakage branch as this has the Demo app upgraded to Rails 5.0.0.1 — incidentally we are also now seeing wymEditor asset issues potentially (?) as a result (as discussed here https://github.com/refinery/refinerycms/issues/3178)