Hashed assets about requirejs-rails HOT 6 CLOSED

I'm not following your request. Can you be more specific?

Currently a build using requirejs-rails (built via rake assets:precompile) produces correctly hashed asset filenames. These will be used by requirejs_include_tag in production. As of v0.6, requirejs_include_tag will also emit a require.js paths config in production to ensure that require('foo') will hit the hashed filename (e.g. foo-123456abcde.js).

What are you looking for beyond this functionality?

from requirejs-rails.

Hrm, although I now note that the above isn't really clearly called out in the README right now. Folks who've been following along for awhile have picked that up from the CHANGELOG and/or announcements on the requirejs group. I'll update the docs on this point.

from requirejs-rails.

Oh I see. Thanks for catching me up on this and the note to use assets:prcompile.

from requirejs-rails.

Reopening to track docs improvement for 1.0 release.

from requirejs-rails.

Here's one thing to note (took me over a day to debug this...):

RequireJS uses the data-main property of its script that to know which module to "require" once the file has been loaded. With hashed filenames, it attempts to load something like "main-980as089asd98f7a2". Since the module is really called "main", it doesn't require it.

This pretty much fails silently. I would advise fixing this method: https://github.com/jwhitley/requirejs-rails/blob/master/app/helpers/requirejs_helper.rb#L10-24 not to keep the hash in the filename.

Here's a quick fix that doesn't require forking the gem:

<%= requirejs_include_tag "main" do
      {"main" => "main"}
    end
%>

from requirejs-rails.

@jeromegn I think that the recent changes on master fixed this, with data-main no longer being used.

from requirejs-rails.