lingo icon indicating copy to clipboard operation
lingo copied to clipboard

项目无法运行

Open haibara-jian opened this issue 1 year ago • 1 comments

node -v v18.12.1 npm -v 9.1.3 yarn -v 1.22.19

yarn serve yarn run v1.22.19 $ vue-cli-service serve INFO Starting development server... 10% building 2/4 modules 2 active /home/ai/iTab/lingo/node_modules/webpack/hot/dev-server.jsnode: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/ai/iTab/lingo/node_modules/webpack/lib/util/createHash.js:135:53) at NormalModule._initBuildHash (/home/ai/iTab/lingo/node_modules/webpack/lib/NormalModule.js:417:16) at handleParseError (/home/ai/iTab/lingo/node_modules/webpack/lib/NormalModule.js:471:10) at /home/ai/iTab/lingo/node_modules/webpack/lib/NormalModule.js:503:5 at /home/ai/iTab/lingo/node_modules/webpack/lib/NormalModule.js:358:12 at /home/ai/iTab/lingo/node_modules/loader-runner/lib/LoaderRunner.js:373:3 at iterateNormalLoaders (/home/ai/iTab/lingo/node_modules/loader-runner/lib/LoaderRunner.js:214:10) at Array. (/home/ai/iTab/lingo/node_modules/loader-runner/lib/LoaderRunner.js:205:4) at Storage.finished (/home/ai/iTab/lingo/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16) at /home/ai/iTab/lingo/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9 at /home/ai/iTab/lingo/node_modules/graceful-fs/graceful-fs.js:123:16 at FSReqCallback.readFileAfterClose [as oncomplete] (node:internal/fs/read_file_context:68:3) { opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ], library: 'digital envelope routines', reason: 'unsupported', code: 'ERR_OSSL_EVP_UNSUPPORTED' }

Node.js v18.12.1 error Command failed with exit code 1. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

haibara-jian avatar Oct 11 '23 08:10 haibara-jian

This project was uploaded two years ago, so encountering issues with the latest version of Node.js is quite normal. You can either downgrade to Node.js v16 or enable legacy OpenSSL provider. Here is a screenshot: Snipaste_2024-01-06_16-22-41

refer: Stack Overflow

tominysun avatar Jan 11 '24 12:01 tominysun