Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incompatibility with multi-core compilation #25

Open
ghost opened this issue Oct 20, 2014 · 3 comments
Open

Incompatibility with multi-core compilation #25

ghost opened this issue Oct 20, 2014 · 3 comments

Comments

@ghost
Copy link

ghost commented Oct 20, 2014

This gem will not work correctly in the context of parallelizing compilation, i.e.

steel/sprockets-derailleur#15

@panasyuk
Copy link

+1

@joshgoebel
Copy link

In application.rb:

class Application < Rails::Application
    # ...
    # require first derailleur, then non-setupid assets that way we're
    # mockey patching the latest version of Sprockets::Manifest
    require "sprockets-derailleur/manifest"
    require "non-stupid-digest-assets"
    NonStupidDigestAssets.whitelist += ["sweet_stuff.js"]

In Gemfile:

gem "non-stupid-digest-assets", require: false # we need to require it later, AFTER sprockets-derailleur

It gets the job done. It makes sure the monkey patching happens against derailleur's own monkey patching. :-)

@joshgoebel
Copy link

Not sure how you could account for this in the gem, but perhaps something like what I posted above could be added to the documentation?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants