We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Yes
node -v
npm -v
yarn --version
npm ls create-elm-app -g
Then, specify:
Launch dev server.
Gives the above.
export NODE_OPTIONS=--openssl-legacy-provider
Quote from person who gave me the fix: "if they update to the latest version of webpack this issue goes away"
The text was updated successfully, but these errors were encountered:
this issue is related to https://nodejs.org/en/blog/vulnerability/openssl-november-2022/ I belive
Sorry, something went wrong.
For powershell i was using: $env:NODE_OPTIONS="--openssl-legacy-provider"
$env:NODE_OPTIONS="--openssl-legacy-provider"
No branches or pull requests
Is this a bug report?
Yes
Environment
node -v
: v17.1.0npm -v
: 8.1.3yarn --version
(if you use Yarn): 1.22.17npm ls create-elm-app -g
(if you haven’t ejected): /usr/local/lib└── [email protected]
Then, specify:
Steps to Reproduce
Expected Behavior
Launch dev server.
Actual Behavior
Gives the above.
Fix
export NODE_OPTIONS=--openssl-legacy-provider
Quote from person who gave me the fix: "if they update to the latest version of webpack this issue goes away"
The text was updated successfully, but these errors were encountered: