Only one requirejs_include_tag allowed per page - why? about requirejs-rails HOT 1 CLOSED

Hi there. Sorry for the delayed response, been down with a cold and playing catch-up. So here's what's going on with require.js itself HTML-wise in your "logged out" case:

<script data-main="/assets/base" src="/assets/require.js"></script>

As I understand it, there are a variety of reasons why it isn't desirable and/or outright breaks if you essentially try to emit another version of the above tag. My offhand sense of what you want to do is more like this:

file setup:
   /assets/common.js     # common code
   /assets/base.js           # your "logged out" base-case
   /assets/logged-in.js

These files would look roughly like this:

// base.js
require(['common'], function (common) {
  // do base stuff
});

// logged-in.js
require(['common'], function (common) {
   // do logged-in stuff
});

Now your layout boilerplate becomes this:

<% if logged_in? %>
  <%= requirejs_include_tag 'logged-in' %>
<% else %>
  <%= requirejs_include_tag 'base' %>
<% end %>

The idea is that your truly common code goes into a module that is picked up by the per-page front-end code. Only one <script> tag for require.js is ever emitted per page this way.

I would also suggest that you hit up the requirejs mailing list and ask around about best practices for per-page setup like this. The above is the "intuitive" solution, but other folks may have ideas and advice that you'll find helpful as well. I'm on the list, so I can help "translate" if needed for any particulars about the gem.

from requirejs-rails.