-
Notifications
You must be signed in to change notification settings - Fork 757
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
Unable to build project on Node version 18 and above #100
Comments
For reference, also an issue in 17 Error: error:0308010C:digital envelope routines::unsupported Node.js v17.9.1 |
Ran into the same issue, using nvm to install node v16.18.1 worked. Thanks! |
Running into this issue as well |
Also having this issue. Most of the advice you find online for resolving this suggests either downgrading to Node 16 or using legacy SSL (for example). These solutions are both insecure and a bit intimidating for newbies who might be coming to Phaser for the first time. Trying to fix it by forcing an update of packages also does not work, as it starts giving errors about upstream dependency conflicts. |
The fix without downgrading the node version is to run Then update the webpack-cli using the force tag this worked with node 18.16.0 and npm 9.5.1 |
Has anyone found solution to this |
After following your instructions and run npm start i am faced with the issue:
clean-webpack-plugin: options.output.path not defined. Plugin disabled... TypeError: Cannot add property htmlWebpackPluginAlterChunks, object is not extensible Node.js v18.14.2` |
I know this thread is a little stale, but to fix these issues, delete the The reason this works is because the lock file is for "locking" down the versions defined in the |
Doesn't work for me. I followed the steps a few times and I get
|
This is fixed with v2.0.0 of this template. |
Thanks |
The project does not build on newer versions of node. I tried on Node version 18.12.1 and 19.1.0. I had to revert Node to LTS Gallium 16.18.1 for the project to build.
The text was updated successfully, but these errors were encountered: