Failed to start app with NodeJS newest version v17.0.1
See original GitHub issue🐛 Bug Report
Starting up the app with the newest NodeJS version (17.0.1) failed with the following error:
npm start
> mydocs@0.0.0 start
> docusaurus start
Starting the development server...
Docusaurus website is running at "http://localhost:3000/".
* Client █████████████████████████ setup (3%)
watch run
node:internal/crypto/hash:67
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:67:19)
at Object.createHash (node:crypto:130:10)
at BulkUpdateDecorator.hashFactory (C:\mydocs\node_modules\webpack\lib\util\createHash.js:155:18)
at BulkUpdateDecorator.digest (C:\mydocs\node_modules\webpack\lib\util\createHash.js:80:21)
at C:\mydocs\node_modules\webpack\lib\DefinePlugin.js:595:38
at _next33 (eval at create (C:\mydocs\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:57:1)
at _next11 (eval at create (C:\mydocs\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:189:1)
at Hook.eval [as call] (eval at create (C:\mydocs\node_modules\tapable\lib\HookCodeFactory.js:19:10), <anonymous>:239:1)
at Hook.CALL_DELEGATE [as _call] (C:\mydocs\node_modules\tapable\lib\Hook.js:14:14)
at Compiler.newCompilation (C:\mydocs\node_modules\webpack\lib\Compiler.js:1053:26)
at C:\mydocs\node_modules\webpack\lib\Compiler.js:1097:29
at Hook.eval [as callAsync] (eval at create (C:\mydocs\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:22:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (C:\mydocs\node_modules\tapable\lib\Hook.js:18:14)
at Compiler.compile (C:\mydocs\node_modules\webpack\lib\Compiler.js:1092:28)
at C:\mydocs\node_modules\webpack\lib\Watching.js:200:19
at Hook.eval [as callAsync] (eval at create (C:\mydocs\node_modules\tapable\lib\HookCodeFactory.js:33:10), <anonymous>:22:1) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v17.0.1
Prerequisites
NodeJS version v17.0.1
Docusaurus newest version 2.0.0-beta.8
- I’m using the latest version of Docusaurus.
- I have tried the
npm run clearoryarn clearcommand. - I have tried
rm -rf node_modules yarn.lock package-lock.jsonand re-installing packages. - I have tried creating a repro with https://new.docusaurus.io
- I have read the console error message carefully (if applicable)
Description
After upgrading Node.js to the newest version (v17.0.1), then creating a new Docusaurus project following the instructions on this page, the project was created successfully but failed when being started with npm start. It seems that there is an error related to Nodejs’s crypto module causing the start of the Docusaurus app crashed.
Have you read the Contributing Guidelines on issues?
YES
Steps to reproduce
Use https://new.docusaurus.io to create a CodeSandbox reproducible demo of the bug.
As we don’t know eactly which Node’s version
CodeSandboxis using, this step is skipped.
- Step 1… Upgrade NodeJS to the newest version
v17.0.1 - Step 2… Create a new
Docusaurusprojectnpm init docusaurus@latest mydocs - Step 3…
cdintomydocsdirectory and runnpm start(currently this command fails to start the app)
Expected behavior
Should be able to start up the app
Your environment
- Public source code:
- Public site URL:
- Docusaurus version used: 2.0.0-beta.8
- Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node.js 17.0.1
- Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows 10
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Node.js 17.0.1 Gatsby error - "digital envelope routines
I have uninstalled Node.js and installed version 16.13.0 and restarted. By running in the new terminal, it got fixed.
Read more >Errors | Node.js v19.3.0 Documentation
User-specified errors triggered by application code. ... Creates a new Error object and sets the error.message property to the provided text message.
Read more >15 Common Error Codes in Node.js and How to Fix Them
15. EPERM · Close all instances of your editor before rerunning the command (maybe some files were locked by the editor). · Clean...
Read more >Download & Update Node.js to the Latest Version! Node v19 ...
Node.js 19 will be 'Current' release for the next 6 months, until April 2023. HTTP(S)/1.1 KeepAlive by default. Starting with this release, ...
Read more >How To Update Node.js on MacOS: Hindsight on Old Mac
js app to be deployed on a production server. You can also pick Current version (2) for the binary with latest / newest...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

At Remotion we managed to fix it using:
output.hashFunctionto “xxhash64”@pkosiec try to re-gen your lockfile and look for older versions of webpack in node modules. If you are using a newer webpack it should work