-
Notifications
You must be signed in to change notification settings - Fork 47
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
Crashes with "Unrecognized source type to auto-detect resource" when imported in NodeJS #199
Comments
Why do you want to do this in an interactive shell? |
In my case, for automated testing. |
To clarify, the issue isn't only in the Node CLI/interactive shell. It's in any Node context. Besides automated tests, library users may want to SSR. |
I think the argument could also be made it's a general usability issue when a module is written such that it assumes and creates a hard dependency on a certain environment at import time? |
In general, Pixi3D has not been created to be imported in any environment. If you want to dig deeper and provide a solution I'm happy to accept a PR. |
Btw, Pixi3D itself has automated tests. Maybe you can have a look at those and see how it works? |
Steps to reproduce
node
interactive shellStack trace
What I expected
It can be imported in Node without crashing. What I've read on in this project's discussions leads me to believe this should be possible.
The text was updated successfully, but these errors were encountered: