reactjs / reactjs/react.dev

Running locally error (Node.js latest LTS Version (12.18.0))

Ouverte
#3,021 5 commentaires 4 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Langage dominant
JavaScript
Étoiles
11.8k
Forks
7.9k
Merge moyen
1 j 11 h
PR mergées (30 j)
11

Description

Here's the log

ahmadrasyidsalim@DESKTOP-MJVOOLR:~/Rasyid/reactjs.org$ node --version
v12.18.0
ahmadrasyidsalim@DESKTOP-MJVOOLR:~/Rasyid/reactjs.org$ yarn --version
1.22.4
ahmadrasyidsalim@DESKTOP-MJVOOLR:~/Rasyid/reactjs.org$ yarn
yarn install v1.22.4
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info fsevents@2.1.2: The platform "linux" is incompatible with this module.
info "fsevents@2.1.2" is an optional dependency and failed compatibility check. Excluding it from installation.
info fsevents@1.2.11: The platform "linux" is incompatible with this module.
info "fsevents@1.2.11" is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning "gatsby > react-hot-loader@4.12.19" has unmet peer dependency "@types/react@^15.0.0 || ^16.0.0".
warning "gatsby > @typescript-eslint/eslint-plugin > tsutils@3.17.1" has unmet peer dependency "typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta".
warning "gatsby-plugin-netlify > webpack-assets-manifest@3.1.1" has unmet peer dependency "webpack@>=4.4.0".
warning " > request-promise@4.2.5" has unmet peer dependency "request@^2.34".
warning "request-promise > request-promise-core@1.1.3" has unmet peer dependency "request@^2.34".
warning " > @babel/preset-flow@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-flow > @babel/plugin-transform-flow-strip-types@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
warning "@babel/preset-flow > @babel/plugin-transform-flow-strip-types > @babel/plugin-syntax-flow@7.8.3" has unmet peer dependency "@babel/core@^7.0.0-0".
[5/5] Building fresh packages...
Done in 214.63s.
ahmadrasyidsalim@DESKTOP-MJVOOLR:~/Rasyid/reactjs.org$ yarn dev
yarn run v1.22.4
$ gatsby develop -H 0.0.0.0
success open and validate gatsby-configs - 0.215s
success load plugins - 11.973s
success onPreInit - 0.096s
success initialize cache - 0.017s
success copy gatsby files - 1.239s
warn gatsby-plugin-feed was initialized in gatsby-config.js without a title in a feed.
This means that the plugin will use the default feed title, which may not match your use case.
This behavior will be removed in the next major release of gatsby-plugin-feed.
For more info, check out: https://gatsby.dev/adding-rss-feed
success onPreBootstrap - 0.039s
success createSchemaCustomization - 1.201s
success source and transform nodes - 2.094s
success building schema - 0.636s
success createPages - 0.991s
success createPagesStatefully - 0.169s
success onPreExtractQueries - 0.004s
success update schema - 0.048s
success extract queries from components - 0.953s
success write out requires - 0.105s
success write out redirect data - 0.015s
success Build manifest and related icons - 0.145s
success onPostBootstrap - 0.159s
⠀
info bootstrap finished - 48.385 s
⠀
success run queries - 0.142s - 71/71 500.68/s

 ERROR #98123  WEBPACK

Generating SSR bundle failed

Cannot find module '@babel/compat-data/corejs3-shipped-proposals'
Require stack:
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/@babel/preset-env/lib/polyfills/corejs3/usage-plugin.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/@babel/preset-env/lib/index.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/@babel/core/lib/config/files/plugins.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/@babel/core/lib/config/files/index.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/@babel/core/lib/index.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/babel-loader/lib/index.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/gatsby/dist/utils/babel-loader.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/loader-runner/lib/loadLoader.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/loader-runner/lib/LoaderRunner.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/webpack/lib/NormalModule.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/webpack/lib/NormalModuleFactory.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/webpack/lib/Compiler.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/webpack/lib/webpack.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/gatsby/dist/commands/develop.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/gatsby-cli/lib/create-cli.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/gatsby-cli/lib/index.js
- /home/ahmadrasyidsalim/Rasyid/reactjs.org/node_modules/gatsby/dist/bin/gatsby.js

File: .cache/develop-static-entry.js



————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
320 pages                                                          In Progress                                                         react-website
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ahmadrasyidsalim@DESKTOP-MJVOOLR:~/Rasyid/reactjs.org$

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Piste de recherche

Reproduisez l’échec avec Node.js 12.18.0 en exécutant yarn et yarn dev dans le dépôt react.dev, puis inspectez l’erreur SSR impliquant .cache/develop-static-entry.js et le @babel preset-env require stack. C’est terminé lorsque le développement local démarre sans l’erreur @babel/compat-data/corejs3-shipped-proposals manquant.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Évaluation

Stack technique
javascript, node.js
Domaine
build-system, web-dev
Type d'issue
Bug
Difficulté
3/5
Temps estimé
1-2 jours
Activité
À l'abandon
Clarté
Plutôt claire
Accessibilité débutants
30/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.