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 v17 bad option: --openssl-legacy-provider #169

Open
predator4hack opened this issue Apr 1, 2022 · 2 comments
Open

Node v17 bad option: --openssl-legacy-provider #169

predator4hack opened this issue Apr 1, 2022 · 2 comments

Comments

@predator4hack
Copy link

Describe the bug
On using the command npm run start, the following error shows up:

> [email protected] start
> react-scripts --openssl-legacy-provider start

/usr/bin/node: bad option: --openssl-legacy-provider

To Reproduce
After clonging the repo,

cd tensorflow-client
npm install
npm run start

Expected behavior
Tensorflow client should start on the localhost

Screenshots
error

Desktop (please complete the following information):

  • OS: Ubuntu 20.04
  • Browser: Chrome
  • Version: 99.0,4

Additional context
It seems that this error shows up because of the Node v17, --openssl-legacy-provider was added for handling key size on OpenSSL v3. Refer this. Although the client runs smoothly if I remove --openssl-legacy-provider in the start script.

@mahmoud-elghonemy
Copy link
Contributor

i solved this problem by eidt "start": "react-scripts start" in package.json file

@priyansh2003
Copy link

Install the react-scripts dependency. That will solve the problem.
Use the command npm install react-scripts.

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