You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a single part of EX is usable outside of the main thread in the browser, making it really hard to use (partially) in workers or in server-side-rendered code without throwing window is not defined. I'm aware that some parts of EX won't be able to function without access to some window specific functionality, but I'm quite sure that something like Vector should be accessible without access to window.
I'm not a library/package expert, so I've no clue where to start searching for a solution, so my main proposal is to use this issue to brainstorm potential reasons/fixes.
The text was updated successfully, but these errors were encountered:
Context
Not a single part of EX is usable outside of the main thread in the browser, making it really hard to use (partially) in workers or in server-side-rendered code without throwing
window is not defined
. I'm aware that some parts of EX won't be able to function without access to somewindow
specific functionality, but I'm quite sure that something likeVector
should be accessible without access towindow
.This will be a good step towards making
Offscreen/off-main thread rendering investigation
for v1.0 viable.Proposal
I'm not a library/package expert, so I've no clue where to start searching for a solution, so my main proposal is to use this issue to brainstorm potential reasons/fixes.
The text was updated successfully, but these errors were encountered: