-
-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev server issue #1020
Comments
Hello, I can confirm the bug both in dev et production. To reproduce, create a new project with the following settings:
Nuxt Infos:
After investigating, the server can be run by using the following environment variable (powershell): Can somebody from the dev team look at it ? Thank you in advance, |
https://stackoverflow.com/questions/69692842/error-message-error0308010cdigital-envelope-routinesunsupported Node version is not LTS and is not supported. Solution is to downgrade or specify legacy openssl version (see links). |
Same warnings and failure to run [01/02/23] 22:09:52 ✝ ~/Projects/training npx create-nuxt-app nuxt-init
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
create-nuxt-app v5.0.0
✨ Generating Nuxt.js project in nuxt-init
? Project name: nuxt-init
? Programming language: JavaScript
? Package manager: Yarn
? UI framework: None
? Template engine: HTML
? Nuxt.js modules: (Press <space> to select, <a> to toggle all, <i> to invert selection)
? Linting tools: ESLint, Prettier
? Testing framework: None
? Rendering mode: Single Page App
? Deployment target: Server (Node.js hosting)
? Development tools: jsconfig.json (Recommended for VS Code if you're not using typescript)
? Continuous integration: None
? Version control system: Git
warning nuxt > @nuxt/babel-preset-app > [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cau
se a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
warning nuxt > @nuxt/webpack > webpack > watchpack > watchpack-chokidar2 > [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies
yarn run v1.22.19
$ prettier --write --list-different . && yarn lint:js --fix
.eslintrc.js
components/NuxtLogo.vue
components/Tutorial.vue
nuxt.config.js
package.json
pages/index.vue
README.md
$ eslint --ext ".js,.vue" --ignore-path .gitignore . --fix
✨ Done in 3.07s.
🎉 Successfully created project nuxt-init
To get started:
cd nuxt-init
yarn dev
To build & start for production:
cd nuxt-init
yarn build
yarn start
npm notice
npm notice New major version of npm available! 8.19.2 -> 9.2.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.2.0
npm notice Run npm install -g [email protected] to update!
npm notice
[01/02/23] 23:50:09 ✝ ~/Projects/training npm install -g [email protected]
removed 14 packages, changed 75 packages, and audited 232 packages in 2s
14 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
Reshimming asdf nodejs...
[01/02/23] 23:50:32 ✝ ~/Projects/training cd nuxt-init/
[01/02/23] 23:50:41 ✝ Projects/training/nuxt-init develop± yarn dev
yarn run v1.22.19
$ nuxt
╭───────────────────────────────────────╮
│ │
│ Nuxt @ v2.15.8 │
│ │
│ ▸ Environment: development │
│ ▸ Rendering: client-side │
│ ▸ Target: server │
│ │
│ Listening: http://localhost:3000/ │
│ │
╰───────────────────────────────────────╯
ℹ Preparing project for development 23:50:49
ℹ Initial build may take a while 23:50:49
ℹ Discovered Components: .nuxt/components/readme.md 23:50:49
✔ Builder initialized 23:50:49
✔ Nuxt files generated 23:50:49
● Client █████████████████████████ compiling (0%)
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 (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/webpack/lib/util/createHash.js:135:53)
at NormalModule._initBuildHash (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/webpack/lib/NormalModule.js:417:16)
at handleParseError (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/webpack/lib/NormalModule.js:471:10)
at /Users/jonhumphrey/Projects/training/nuxt-init/node_modules/webpack/lib/NormalModule.js:503:5
at /Users/jonhumphrey/Projects/training/nuxt-init/node_modules/webpack/lib/NormalModule.js:358:12
at /Users/jonhumphrey/Projects/training/nuxt-init/node_modules/loader-runner/lib/LoaderRunner.js:373:3
at iterateNormalLoaders (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/loader-runner/lib/LoaderRunner.js:214:10)
at Array.<anonymous> (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/loader-runner/lib/LoaderRunner.js:205:4)
at Storage.finished (/Users/jonhumphrey/Projects/training/nuxt-init/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:55:16)
at /Users/jonhumphrey/Projects/training/nuxt-init/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:91:9
at /Users/jonhumphrey/Projects/training/nuxt-init/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'
} |
Version
create-nuxt-app: 5.0.0
npm: 9.1.2
node: 19.1.0
Steps to reproduce
What is Expected?
What is actually happening?
The text was updated successfully, but these errors were encountered: