reactjs / reactjs/react.dev

[Typo]: Cannot debug the react source code through 'babel-standalone/dev.html' file

Open
#6,833 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: typos
Dominant language
JavaScript
Stars
11.8k
Forks
7.9k
Avg merge
1d 11h
Merged PRs (30d)
11

Description

Summary

Follow this link to debug the react source code yet failed:
https://legacy.reactjs.org/docs/how-to-contribute.html

Steps:
1). Make no changes to main branch and just run the yarn build command
2). Open the fixtures/packaging/babel-standalone/dev.html file which includes your changes, but meet the errors from browser console as below:

GET file:///Users/quinvon/Documents/GitHub/react/build/oss-experimental/react/umd/react.development.js net::ERR_FILE_NOT_FOUND
dev.html:4 
        
        
       GET file:///Users/quinvon/Documents/GitHub/react/build/oss-experimental/react-dom/umd/react-dom.development.js net::ERR_FILE_NOT_FOUND
babel.js:61666 You are using the in-browser Babel transformer. Be sure to precompile your scripts for production - https://babeljs.io/docs/setup/
runScripts @ babel.js:61666
transformScriptTags @ babel.js:336
(anonymous) @ babel.js:327
Inline Babel script:2 Uncaught ReferenceError: ReactDOM is not defined

I think your debug way of source code is out of date!

Page

https://legacy.reactjs.org/docs/how-to-contribute.html

Details

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the contribution instructions at legacy.reactjs.org/docs/how-to-contribute.html and the referenced fixtures/packaging/babel-standalone/dev.html file, then reproduce the documented yarn build and browser-console errors. Done means the documentation's source-debugging steps match the current build output and no longer lead to missing React or ReactDOM files.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.