Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Build: Add Safari 10.1 nomodule fix

See original GitHub issue

Safari 10.1 supports modules, but does not support the nomodule attribute - it will load <script nomodule> anyway.

Reference: Modern Script Loading

First, there’s the Safari Fix. Safari 10.1 supports JS Modules not the nomodule attribute on scripts, which causes it to execute both the modern and legacy code (yikes!).

Thankfully, Sam found a way to use a non-standard beforeload event supported in Safari 10 & 11 to polyfill nomodule.

Issue Analytics

State:
Created 4 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

LarsDenBakkercommented, Jul 23, 2019

We don’t use <script nomodule> for loading the application though, only for a few polyfills. We use a check in javascript so it won’t load both versions of the application if I understand it correctly.

I will do some tests to see how it’s working out right now on 10.1

0reactions

stale[bot]commented, Sep 17, 2019

Hey there, it’s me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Open Web Components!