Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
Safari 10.1 `nomodule` support
* Safari 10.1 supports modules, but does not support the `nomodule` attribute - it will
* load <script nomodule> anyway. This snippet solve this problem, but only for script
* tags that load external code, e.g.: <script nomodule src="nomodule.js"></script>
* Again: this will **not** prevent inline script, e.g.:
* <script nomodule>alert('no modules');</script>.
* This workaround is possible because Safari supports the non-standard 'beforeload' event.
* This allows us to trap the module and nomodule load.
* Note also that `nomodule` is supported in later versions of Safari - it's just 10.1 that
* omits this attribute.
(function() {
var check = document.createElement('script');
if (!('noModule' in check) && 'onbeforeload' in check) {
var support = false;
document.addEventListener('beforeload', function(e) {
if ( === check) {
support = true;
} else if (!'nomodule') || !support) {
}, true);
check.type = 'module';
check.src = '.';
* Minified-ish version of the above.
(function() {
var d = document;
var c = d.createElement('script');
if (!('noModule' in c) && 'onbeforeload' in c) {
var s = false;
d.addEventListener('beforeload', function(e) {
if ( === c) {
s = true;
} else if (!'nomodule') || !s) {
}, true);
c.type = 'module';
c.src = '.';

This is pretty smart!

anilanar commented Jun 25, 2017

Safari 10.1 still downloads the nomodule file, but it doesn't execute.

My fork:
Not as easy to use as the original one as scripts are injected at runtime.


samthor commented Sep 12, 2017

Hey everyone! This approach works but has its challenges—Safari might still download the script, even though it won't execute, which is not ideal (but it is a limited version of Safari that this issue effects).

A simpler approach, although it involves adding more hacks to your actual code, is to create your ES Modules / nomodule scripts in this order:

<script type="module" src="module.js"></script>
<script src="nomodule.js" nomodule defer></script>

The key here is the defer attribute. As ES Modules scripts are deferred by default, you want your older code to run in the same way—after the page is loaded—so they will run in a consistent order.

And then inside the nomodule.js file, check whether your code has already executed: e.g. if (window._yourCodeLoaded) { throw new Error("safari 10.1 has a bug); }.

@samthor Would you suggest dynamically inserting a new script tag in the deferred nomodule script (in case the module script has not been loaded / the flag has not been set by the main code)?

@samthor You're missing the closing double quote: if (window._yourCodeLoaded) { throw new Error("safari 10.1 has a bug"); }

@niklaskorz I believe setting defer on the second script guarantees that it runs after the earlier already-defer-ed script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment