Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixing global window reliance of Excalibur #3175

Open
Autsider666 opened this issue Aug 20, 2024 · 0 comments
Open

Fixing global window reliance of Excalibur #3175

Autsider666 opened this issue Aug 20, 2024 · 0 comments

Comments

@Autsider666
Copy link
Contributor

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 some window specific functionality, but I'm quite sure that something like Vector should be accessible without access to window.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant