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

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS #197

Open
joshuacheong opened this issue Aug 26, 2022 · 3 comments
Open

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS #197

joshuacheong opened this issue Aug 26, 2022 · 3 comments

Comments

@joshuacheong
Copy link

I am facing this issue. Any ideas to resolve will be appreciated.
`$ npm start

[email protected] start
NODE_OPTIONS=--openssl-legacy-provider gatsby develop

node: --openssl-legacy-provider is not allowed in NODE_OPTIONS`

@ajrequenez
Copy link
Contributor

I ran into the same issue. After i updated all my dependencies I think that option is no longer needed. Try running gatsby directly with npx gatsby develop. This worked for me so I removed that option from the npm start script and it's working fine for me now.

Hope this helps

@melonicedlatte
Copy link

In my case, i change package.json file.
I delete NODE_OPTIONS=--openssl-legacy-provider option.

@joshuacheong
Copy link
Author

Ok let me try that and see if it works. Will let you know.

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

3 participants