rebus
rebus copied to clipboard
npm start not working
Expected Behavior
should start the local server and launch the app
...
Actual Behavior
[email protected] start webpack-dev-server --mode development
(node:9424) [DEP0111] DeprecationWarning: Access to process.binding('http_parser') is deprecated.
(Use node --trace-deprecation ...
to show where the warning was created)
i ï½¢wdsï½£: Project is running at http://localhost:3000/
i ï½¢wdsï½£: webpack output is served from /
i ï½¢wdsï½£: Content not from webpack is served from C:\Users\ojasv\rebus\dist
node:internal/crypto/hash:69
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:69:19)
at Object.createHash (node:crypto:138:10)
at module.exports (C:\Users\ojasv\rebus\node_modules\webpack\lib\util\createHash.js:90:53)
at NormalModule._initBuildHash (C:\Users\ojasv\rebus\node_modules\webpack\lib\NormalModule.js:386:16)
at handleParseError (C:\Users\ojasv\rebus\node_modules\webpack\lib\NormalModule.js:434:10)
at C:\Users\ojasv\rebus\node_modules\webpack\lib\NormalModule.js:466:5
at C:\Users\ojasv\rebus\node_modules\webpack\lib\NormalModule.js:327:12
at C:\Users\ojasv\rebus\node_modules\loader-runner\lib\LoaderRunner.js:370:3
at iterateNormalLoaders (C:\Users\ojasv\rebus\node_modules\loader-runner\lib\LoaderRunner.js:211:10)
at Array.
...
Steps to Reproduce the Problem
- Step 1..
- Step 2..
- Step 3..
Specifications
- Browser: google chrome
Hey @PoseidonSaan, I want to solve this issue please assign this to me. Thanks
Hey @PoseidonSaan, this thread worked for me.
I ran set NODE_OPTIONS=--openssl-legacy-provider
in command prompt & It worked. Hope it helps : ).
Hey @PoseidonSaan, I want to solve this issue please assign this to me. Thanks
Hey @PoseidonSaan, this thread worked for me. I ran
set NODE_OPTIONS=--openssl-legacy-provider
in command prompt & It worked. Hope it helps : ).
I tried this but this is not working for me
Hi! 👋 I am also facing the same issue 😟 Can someone suggest the possible solution?
Hey @PoseidonSaan This issue occurs when you use node version 16+. As @wchetan mentioned you can use the command. Assign this issue to me I will update package.json