Requires are always put above any code that precedes them.

[meh]

This is a sprockets constraint, we have to find a solution because it becomes impossible to run code in gems, it's also extremely unintuitive.

[adambeynon]

This is a inherited problem from using sprockets. If we want to be able to require files in an exact place in ruby code, then we would probably have to add some client side storage of compiled files to be able to load them, e.g.:

opal.register('opal/array', function() { … });
opal.register('parslet', function() { … });
opal.register('parslet/foo', function() { … });

And then require would work off some opal function:

opal.require = function(path) { … };

Or, we could add some parser subclass for shooting off to require.js, or something similar, which could handle that for us.

(For what its worth, I will personally continue using opal-sprockets, but it is now removed from core, so opal-require-ms or similar would be just as useful).

[adambeynon]

Moving this to opal-sprockets as it belongs there (opal just compiles code, opal-sprockets is responsible for handling concatenation of code).