-
-
Notifications
You must be signed in to change notification settings - Fork 359
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 run dev with new node 18 on Mac #5961
Comments
It builds without that. ![]() cc @preschian ? |
hhmm, let me open the PR to remove that. afaik in the pipelines will fail, so we need to add that env on github actions, netlify, and cf |
Build ok for me on OSX > nuxi prepare && cross-env NODE_OPTIONS=--openssl-legacy-provider PORT=9090 nuxi dev
Nuxi 3.0.0 08:58:43
✔ Sentry reporting is enabled (client side: enabled, server side: enabled) nuxt:sentry 08:58:44
ℹ Production build 08:58:44
ℹ Bundling only for client side 08:58:44
ℹ Target: static 08:58:44
ℹ Using components loader to optimize imports 08:58:44
ℹ Discovered Components: .nuxt/components/readme.md 08:58:44
✔ Builder initialized 08:58:44
✔ Nuxt files generated 08:58:44
✔ Types generated in .nuxt 08:58:44
08:59:27
✔ Client
Compiled successfully in 40.76s
✔ Nitro built in 186 ms nitro 08:59:34
ℹ Waiting for file changes What's in |
interesting, does it fails in your local if remove |
Yes, fail |
To update to node 18 I've just:
|
Research for #5979 |
What happened?
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
Please reproduce in steps
To be able to build
Expected Behavior
~
What browsers are you seeing the problem on?
No response
At which address did you encounter bug?
No response
Are you logged in?
None
Which wallet you are using?
No response
At which chain did you encounter bug?
No response
Screenshots
Relevant log output
No response
Payment link for reward
https://kodadot.xyz/transfer/?target=%3CMy_Kusama_Address_check_https://github.com/kodadot/nft-gallery/blob/main/CONTRIBUTING.md#creating-your-ksm-address%3E
Code of Conduct
The text was updated successfully, but these errors were encountered: