-
-
Notifications
You must be signed in to change notification settings - Fork 867
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
Attempting to import into ES6 yields error #821
Comments
does this format work for you:
|
see this thread: #89 (comment) |
Interesting, I am not using nextjs to my knowledge, unless Phaser uses that under the hood. |
Same result. Console:
|
It doesn't look like Phaser uses NextJS under the hood. I don't have a next.config.js file to modify. |
I still get "process not defined" |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior:
Import dotenv using the instructions in the readme.md
Actual Behavior:
Yields an error in Chrome
notes:
Error files: I have preserved the error in a branch of my project.
IDE: VSCode
Browser: Chrome Version 122.0.6261.129 (Official Build) (64-bit)
OS: Windows 10
The text was updated successfully, but these errors were encountered: