Almond timing issue page load about almond

[jrburke]

It depends on when you load almond, but I can see this happening -- almond executes any require([]) calls inserted by insertRequire after the current spin of the event loop, so if you want the module directly after that require([]) call it will probably not be there.

requirejs will be changed in a future release, requirejs/requirejs#373, to match this behavior, since it is more correct.

So the trick then is to work out the page logic to match that execution model in almond since that will be more future compatible. I did not quite follow the sequence of events in the description. If you have code or code samples that might work better if you want some suggestions on how to construct the code.

Going to close this for now for bug triage, but please feel free to continue the discussion here, and if an issue is uncovered, we can reopen.

[sowelie]

Hey John, thanks for the quick response! Also, thank you for your hard work, RequireJS is awesome and it is really helping the development process for me.

What I'm looking to do is basically make the module loading seamless to the end user. I want them to be able to include my bundled JS file (which was built by the RequireJS optimizer) and then as soon as the page load event fires, I want them to be able to access all of the code that was loaded in the bundled JS file.

Is this possible to accomplish with almond? Would it make more sense for the RequireJS optimizer to order the code in the bundle properly and remove the define / require calls (thus completely removing the reliance on an AMD loader)?

[jrburke]

almond right now allows synchronous access at the top level require level to modules by doing:

require('foo');

However, this is not portable to other AMD loaders (even requirejs), and is not a standard feature for top-level require() APIs (it can work for local require('') API calls inside modules though).

So if you are OK sticking with almond, then I would probably do something in a wrap.end or wrap.endFile that would expose your code in the global space by using the require('foo') to get the modules.

[sowelie]

This seems to work just fine! For this version of my script I will only ever be relying on the AMD module of my choice.