-
Notifications
You must be signed in to change notification settings - Fork 116
unable to resolve dependency tree #70
Comments
Please try with 'yarn install' |
That worked for me, perhaps the README should be updated if yarn should be used. |
Perhaps related, I also receive errors when trying to run the examples (Pop!_OS 22.04). npm run examples
> [email protected] examples
> webpack-dev-server --content-base src-examples/ --config config/webpack.config.examples.js --mode development --open
ℹ 「wds」: Project is running at http://localhost:8080/
ℹ 「wds」: webpack output is served from /
ℹ 「wds」: Content not from webpack is served from /home/curiouser/Sites/tmp/src-examples
ℹ 「wds」: 404s will fallback to /index.html
node:internal/crypto/hash:71
this[kHandle] = new _Hash(algorithm, xofLen);
^
Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at module.exports (/home/curiouser/Sites/tmp/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/home/curiouser/Sites/tmp/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/home/curiouser/Sites/tmp/node_modules/webpack/lib/NormalModule.js:471:10)
at /home/curiouser/Sites/tmp/node_modules/webpack/lib/NormalModule.js:503:5
at /home/curiouser/Sites/tmp/node_modules/webpack/lib/NormalModule.js:358:12
at /home/curiouser/Sites/tmp/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/home/curiouser/Sites/tmp/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array.<anonymous> (/home/curiouser/Sites/tmp/node_modules/loader-runner/lib/LoaderRunner.js:205:4) {
opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
Node.js v18.16.0 I'm using nvm, so the simple workaround is to simple nvm use 16
npm run examples |
Please try with 'yarn run examples' 😊 |
Not quite as simple this time :p |
I am running in PowerShell. Does it matter?
|
On a fresh clone using
npm 8.19.3
node v18.13.0
The text was updated successfully, but these errors were encountered: