Problem with config.asstes.precompile() about requirejs-rails HOT 2 CLOSED

Hi @skorth, currently this is by design. requirejs-rails takes over the JavaScript side of the Rails asset pipeline. Any asset path name that contains javascripts is handled by the gem's build process, not by the asset pipeline.

There are two workarounds that come to mind. First, you could just use the order! plugin to bring in the non-module code. For example, in application.js:

require( ['jquery', 'underscore', 'order!rails'], function ($, _) {
  // ...
}

This is the approach I use in one app to pull in non-AMD libraries such as d3.

The second workaround avoids require.js completely. Create a new asset path for your non-module JavaScripts, like so:

# rails.js should now live in app/assets/non-amd

config.asset.paths << Rails.root.join("app","assets","non-amd")
config.assets.precompile += %w( rails.js admin/admin.css )

Any directory name other than javascripts should work just fine. requirejs-rails won't see it, and the traditional Rails asset pipeline will.

from requirejs-rails.

Hey @jwhitley,

thanks alot! I use the second approach like you suggested (http://guides.rubyonrails.org/asset_pipeline.html#asset-organization) and it works great. Would be nice to see a small advice within the readme.

Thanks for this great Gem!

from requirejs-rails.