Reposted by Max Patiiuk
Just ran into this bug in #safari bugs.webkit.org/show_bug.cgi...
And it means using top-level await is essentially a no-go if you need to support Safari. Just when I thought they were making good strides in a good direction, we still often run into such issues, like in the time of IE 😭
And it means using top-level await is essentially a no-go if you need to support Safari. Just when I thought they were making good strides in a good direction, we still often run into such issues, like in the time of IE 😭
242740 – [JSC] ReferenceError when multiple modules are simultaneously importing a module containing a top-level await
bugs.webkit.org
February 25, 2025 at 7:51 PM
Just ran into this bug in #safari bugs.webkit.org/show_bug.cgi...
And it means using top-level await is essentially a no-go if you need to support Safari. Just when I thought they were making good strides in a good direction, we still often run into such issues, like in the time of IE 😭
And it means using top-level await is essentially a no-go if you need to support Safari. Just when I thought they were making good strides in a good direction, we still often run into such issues, like in the time of IE 😭