Open MrCaira opened 2 years ago
Use Git Bash
Navigate to the boilerplate directory
Use this command: export NODE_OPTIONS=--openssl-legacy-provider
Then it should work
Use Git Bash Navigate to the boilerplate directory Use this command:
export NODE_OPTIONS=--openssl-legacy-provider
Then it should work
This command is for Linux/mac os, however $env:NODE_OPTIONS = "--openssl-legacy-provider
works in windows.
after applying your code its coming like that
after applying your code its coming like that
You have to end the quote for "--openssl-legacy-provider"
$env:NODE_OPTIONS = "--openssl-legacy-provider
You Are Great! Thankyou Very Much Brother Thanks A Lot @thomasjvu
thanks @thomasjvu
It's not working for me. I used npm install and then I got this error:
25 packages are looking for funding run
npm fund` for details
38 vulnerabilities (8 moderate, 24 high, 6 critical)
To address all issues, run: npm audit fix
Run npm audit
for details.`
@Z-Hp just ignore and start it when i use yarn it alert
info This module is OPTIONAL, you can safely ignore this error
Strange. It opens up a tab for me saying "localhost:3000", yet the tab refuses to connect. When I inspect, it says "non-JS module files deprecated". Does this suggest its a network problem?? Then that's weird, because I have totally normal network.
people should upgrade the packages "@babel/core": "^7.24.5", "@babel/preset-env": "^7.24.5", "babel-loader": "^9.1.3", "browser-sync": "^2.29.3", "browser-sync-webpack-plugin": "^2.3.0", "file-loader": "^6.2.0", "html-webpack-plugin": "^5.6.0", "prettier": "^3.2.5", "webpack": "^5.91.0", "webpack-cli": "^5.1.4"
The project wont work at all for me, using npm start prompts following error on Windows 11.
I freshly installed nodejs less than 1 hour ago, on a clean Windows 11 system. Running node v18.4.0. Just cloned and did npm install, and have not touched files in between or after at all.