I’d be curious to know where RequireJS trips up?
Alex Mills
11

RequireJS is interesting because it’s designed to be an AMD loader, so if you write all your scripts that way then it’s possible you’ll never see a problem – the loaded script calling `define` is effectively skirting the issue of needing an `onload` callback.

If you try to make full use of RequireJS’ features, like `shim` for scripts that don’t call `define`, then its claimed browser support breaks down: it fails the same way all the other loaders do by not emulating atomic `onload` behavior correctly. And even though IE10 has the correct behavior without any extra work, it fails to detect support for it : https://github.com/jrburke/requirejs/issues/526

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.