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

Issue while running command "npm start". #9

Open
rnikhil3520 opened this issue Oct 8, 2022 · 3 comments
Open

Issue while running command "npm start". #9

rnikhil3520 opened this issue Oct 8, 2022 · 3 comments

Comments

@rnikhil3520
Copy link

While running command "npm start" after "npm install". It doesn't respond well and shows "node: bad option: --openssl-legacy-provider".

@rnikhil3520
Copy link
Author

Issues Resolved in following Pull request

#10

@isoteriksoftware
Copy link

@rnikhil3520 you're likely using the wrong version of Node.js. You need v18+

@yyccPhil
Copy link

yyccPhil commented Nov 9, 2022

I have also met the same issue when I used latest version of node, it will solve using 18.10.0 version. To install a specific version of node, consider using nvm (https://github.com/nvm-sh/nvm).

But I want to share another issue after I installed correct version of node by nvm. While running command "npm start", it shows "env: node: No such file or directory".
I searched and found it was because I used homebrew to install nvm and did not add the nvm path.
To solve that here are two solution:
run "source ~/.nvm/nvm.sh" command first OR just put it in the file /.bashrc or ~/.profile or ~/.zshrc to automatically load it.

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