\n This page doesn’t appear to be using React.<\/b>\n
\n- If this seems wrong, follow the troubleshooting instructions<\/a>.\n+ If this seems wrong, follow the troubleshooting instructions<\/a>.\n <\/p>\ndiff --git a\/packages\/react-devtools-inline\/README.md b\/packages\/react-devtools-inline\/README.md\nindex c523ed3107..22cff37fb7 100644\n--- a\/packages\/react-devtools-inline\/README.md\n+++ b\/packages\/react-devtools-inline\/README.md\n@@ -211,4 +211,4 @@ Once the above packages have been built or downloaded, you can watch for changes\n yarn start\n ```\n \n-To test package changes, refer to the [`react-devtools-shell` README](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-devtools-shell\/README.md).\n+To test package changes, refer to the [`react-devtools-shell` README](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-devtools-shell\/README.md).\ndiff --git a\/packages\/react-devtools-scheduling-profiler\/src\/view-base\/utils\/normalizeWheel.js b\/packages\/react-devtools-scheduling-profiler\/src\/view-base\/utils\/normalizeWheel.js\nindex 6e783a0fc0..89de907562 100644\n--- a\/packages\/react-devtools-scheduling-profiler\/src\/view-base\/utils\/normalizeWheel.js\n+++ b\/packages\/react-devtools-scheduling-profiler\/src\/view-base\/utils\/normalizeWheel.js\n@@ -7,7 +7,7 @@\n * @flow\n *\/\n \n-\/\/ Adapted from: https:\/\/github.com\/facebookarchive\/fixed-data-table\/blob\/master\/src\/vendor_upstream\/dom\/normalizeWheel.js\n+\/\/ Adapted from: https:\/\/github.com\/facebookarchive\/fixed-data-table\/blob\/main\/src\/vendor_upstream\/dom\/normalizeWheel.js\n \n export type NormalizedWheelDelta = {|\n deltaX: number,\ndiff --git a\/packages\/react-devtools-shared\/src\/__tests__\/profilingCache-test.js b\/packages\/react-devtools-shared\/src\/__tests__\/profilingCache-test.js\nindex ace43294e9..2cf31e867b 100644\n--- a\/packages\/react-devtools-shared\/src\/__tests__\/profilingCache-test.js\n+++ b\/packages\/react-devtools-shared\/src\/__tests__\/profilingCache-test.js\n@@ -672,7 +672,7 @@ describe('ProfilingCache', () => {\n \n const About = () =>

About<\/div>;\n \n- \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/master\/packages\/react-router\/modules\/Router.js\n+ \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/main\/packages\/react-router\/modules\/Router.js\n function Router({children}) {\n const [path, setPath] = React.useState('\/');\n return (\n@@ -682,7 +682,7 @@ describe('ProfilingCache', () => {\n );\n }\n \n- \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/master\/packages\/react-router\/modules\/Switch.js\n+ \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/main\/packages\/react-router\/modules\/Switch.js\n function Switch({children}) {\n return (\n \n@@ -699,14 +699,14 @@ describe('ProfilingCache', () => {\n );\n }\n \n- \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/master\/packages\/react-router\/modules\/Route.js\n+ \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/main\/packages\/react-router\/modules\/Route.js\n function Route({children, path}) {\n return null;\n }\n \n const linkRef = React.createRef();\n \n- \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/master\/packages\/react-router-dom\/modules\/Link.js\n+ \/\/ Mimics https:\/\/github.com\/ReactTraining\/react-router\/blob\/main\/packages\/react-router-dom\/modules\/Link.js\n function Link({children, path}) {\n return (\n \ndiff --git a\/packages\/react-devtools-shared\/src\/backend\/renderer.js b\/packages\/react-devtools-shared\/src\/backend\/renderer.js\nindex 2911855f57..d9aa2672d4 100644\n--- a\/packages\/react-devtools-shared\/src\/backend\/renderer.js\n+++ b\/packages\/react-devtools-shared\/src\/backend\/renderer.js\n@@ -2633,7 +2633,7 @@ export function attach(\n const UNMOUNTED = 3;\n \n \/\/ This function is copied from React and should be kept in sync:\n- \/\/ https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-reconciler\/src\/ReactFiberTreeReflection.js\n+ \/\/ https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-reconciler\/src\/ReactFiberTreeReflection.js\n function isFiberMountedImpl(fiber: Fiber): number {\n let node = fiber;\n let prevNode = null;\n@@ -2689,7 +2689,7 @@ export function attach(\n }\n \n \/\/ This function is copied from React and should be kept in sync:\n- \/\/ https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-reconciler\/src\/ReactFiberTreeReflection.js\n+ \/\/ https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-reconciler\/src\/ReactFiberTreeReflection.js\n \/\/ It would be nice if we updated React to inject this function directly (vs just indirectly via findDOMNode).\n \/\/ BEGIN copied code\n function findCurrentFiberUsingSlowPathById(id: number): Fiber | null {\ndiff --git a\/packages\/react-devtools-shared\/src\/constants.js b\/packages\/react-devtools-shared\/src\/constants.js\nindex 7babb90cff..a5449612c7 100644\n--- a\/packages\/react-devtools-shared\/src\/constants.js\n+++ b\/packages\/react-devtools-shared\/src\/constants.js\n@@ -44,7 +44,7 @@ export const LOCAL_STORAGE_TRACE_UPDATES_ENABLED_KEY =\n export const PROFILER_EXPORT_VERSION = 5;\n \n export const CHANGE_LOG_URL =\n- 'https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-devtools\/CHANGELOG.md';\n+ 'https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-devtools\/CHANGELOG.md';\n \n export const UNSUPPORTED_VERSION_URL =\n 'https:\/\/reactjs.org\/blog\/2019\/08\/15\/new-react-devtools.html#how-do-i-get-the-old-version-back';\ndiff --git a\/packages\/react-devtools-shared\/src\/devtools\/cache.js b\/packages\/react-devtools-shared\/src\/devtools\/cache.js\nindex cc51b31861..c98b0566d8 100644\n--- a\/packages\/react-devtools-shared\/src\/devtools\/cache.js\n+++ b\/packages\/react-devtools-shared\/src\/devtools\/cache.js\n@@ -15,7 +15,7 @@ import {createContext} from 'react';\n \/\/ TODO (cache) Remove this cache; it is outdated and will not work with newer APIs like startTransition.\n \n \/\/ Cache implementation was forked from the React repo:\n-\/\/ https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-cache\/src\/ReactCache.js\n+\/\/ https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-cache\/src\/ReactCache.js\n \/\/\n \/\/ This cache is simpler than react-cache in that:\n \/\/ 1. Individual items don't need to be invalidated.\ndiff --git a\/packages\/react-devtools-shell\/README.md b\/packages\/react-devtools-shell\/README.md\nindex 0ad5de70b9..6d1d3b76dc 100644\n--- a\/packages\/react-devtools-shell\/README.md\n+++ b\/packages\/react-devtools-shell\/README.md\n@@ -2,7 +2,7 @@ Harness for testing local changes to the `react-devtools-inline` and `react-devt\n \n ## Development\n \n-This target should be run in parallel with the `react-devtools-inline` package. The first step then is to run that target following the instructions in the [`react-devtools-inline` README](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-devtools-inline\/README.md).\n+This target should be run in parallel with the `react-devtools-inline` package. The first step then is to run that target following the instructions in the [`react-devtools-inline` README](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-devtools-inline\/README.md).\n \n The test harness can then be run as follows:\n ```sh\ndiff --git a\/packages\/react-devtools\/CHANGELOG.md b\/packages\/react-devtools\/CHANGELOG.md\nindex f07db005bb..ec244e939c 100644\n--- a\/packages\/react-devtools\/CHANGELOG.md\n+++ b\/packages\/react-devtools\/CHANGELOG.md\n@@ -2,7 +2,7 @@\n \n
\n
\n- Changes that have landed in master but are not yet released.\n+ Changes that have landed in main but are not yet released.\n Click to see more.\n <\/summary>\n \n@@ -380,7 +380,7 @@ New keys can be added to object props\/state\/hooks now. Existing keys can be rena\n #### Improved performance\n The legacy DevTools extension used to add significant performance overhead, making it unusable for some larger React applications. That overhead has been effectively eliminated in version 4.\n \n-[Learn more](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-devtools\/OVERVIEW.md) about the performance optimizations that made this possible.\n+[Learn more](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-devtools\/OVERVIEW.md) about the performance optimizations that made this possible.\n \n #### Component stacks\n \n@@ -406,7 +406,7 @@ Filter preferences are remembered between sessions.\n \n #### No more inline props\n \n-Components in the tree no longer show inline props. This was done to [make DevTools faster](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-devtools\/OVERVIEW.md) and to make it easier to browse larger component trees.\n+Components in the tree no longer show inline props. This was done to [make DevTools faster](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-devtools\/OVERVIEW.md) and to make it easier to browse larger component trees.\n \n You can view a component's props, state, and hooks by selecting it:\n \ndiff --git a\/packages\/react-devtools\/OVERVIEW.md b\/packages\/react-devtools\/OVERVIEW.md\nindex 0c8d47da26..a05bafc3b2 100644\n--- a\/packages\/react-devtools\/OVERVIEW.md\n+++ b\/packages\/react-devtools\/OVERVIEW.md\n@@ -259,7 +259,7 @@ Even when dealing with a single component, serializing deeply nested properties\n \n Hooks present a unique challenge for the DevTools because of the concept of _custom_ hooks. (A custom hook is essentially any function that calls at least one of the built-in hooks. By convention custom hooks also have names that begin with \"use\".)\n \n-So how does DevTools identify custom functions called from within third party components? It does this by temporarily overriding React's built-in hooks and shallow rendering the component in question. Whenever one of the (overridden) built-in hooks are called, it parses the call stack to spot potential custom hooks (functions between the component itself and the built-in hook). This approach enables it to build a tree structure describing all of the calls to both the built-in _and_ custom hooks, along with the values passed to those hooks. (If you're interested in learning more about this, [here is the source code](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-debug-tools\/src\/ReactDebugHooks.js).)\n+So how does DevTools identify custom functions called from within third party components? It does this by temporarily overriding React's built-in hooks and shallow rendering the component in question. Whenever one of the (overridden) built-in hooks are called, it parses the call stack to spot potential custom hooks (functions between the component itself and the built-in hook). This approach enables it to build a tree structure describing all of the calls to both the built-in _and_ custom hooks, along with the values passed to those hooks. (If you're interested in learning more about this, [here is the source code](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-debug-tools\/src\/ReactDebugHooks.js).)\n \n > **Note**: DevTools obtains hooks info by re-rendering a component.\n > Breakpoints will be invoked during this additional (shallow) render,\ndiff --git a\/packages\/react-devtools\/README.md b\/packages\/react-devtools\/README.md\nindex 2551416b97..a8794737c0 100644\n--- a\/packages\/react-devtools\/README.md\n+++ b\/packages\/react-devtools\/README.md\n@@ -105,7 +105,7 @@ Or you could develop with a local HTTP server [like `serve`](https:\/\/www.npmjs.c\n \n **If your app is inside of CodePen**, make sure you are registered. Then press Fork (if it's not your pen), and then choose Change View > Debug. The Debug view is inspectable with DevTools because it doesn't use an iframe.\n \n-**If your app is inside an iframe, a Chrome extension, React Native, or in another unusual environment**, try [the standalone version instead](https:\/\/github.com\/facebook\/react\/tree\/master\/packages\/react-devtools). Chrome apps are currently not inspectable.\n+**If your app is inside an iframe, a Chrome extension, React Native, or in another unusual environment**, try [the standalone version instead](https:\/\/github.com\/facebook\/react\/tree\/main\/packages\/react-devtools). Chrome apps are currently not inspectable.\n \n **If you still have issues** please [report them](https:\/\/github.com\/facebook\/react\/issues\/new?labels=Component:%20Developer%20Tools). Don't forget to specify your OS, browser version, extension version, and the exact instructions to reproduce the issue with a screenshot.\n \ndiff --git a\/packages\/react-reconciler\/README.md b\/packages\/react-reconciler\/README.md\nindex ec15ffd274..8b0fc1b9ea 100644\n--- a\/packages\/react-reconciler\/README.md\n+++ b\/packages\/react-reconciler\/README.md\n@@ -51,15 +51,15 @@ const HostConfig = {\n * **[Building a simple custom renderer to DOM](https:\/\/medium.com\/@agent_hunt\/hello-world-custom-react-renderer-9a95b7cd04bc)**\n * **[Building a simple custom renderer to native](https:\/\/medium.com\/@agent_hunt\/introduction-to-react-native-renderers-aka-react-native-is-the-java-and-react-native-renderers-are-828a0022f433)**\n \n-The full list of supported methods [can be found here](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). For their signatures, we recommend looking at specific examples below.\n+The full list of supported methods [can be found here](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). For their signatures, we recommend looking at specific examples below.\n \n The React repository includes several renderers. Each of them has its own host config.\n \n The examples in the React repository are declared a bit differently than a third-party renderer would be. In particular, the `HostConfig` object mentioned above is never explicitly declared, and instead is a *module* in our code. However, its exports correspond directly to properties on a `HostConfig` object you'd need to declare in your code:\n \n-* [React ART](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-art\/src\/ReactART.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-art\/src\/ReactARTHostConfig.js)\n-* [React DOM](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-dom\/src\/client\/ReactDOM.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-dom\/src\/client\/ReactDOMHostConfig.js)\n-* [React Native](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-native-renderer\/src\/ReactNativeRenderer.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-native-renderer\/src\/ReactNativeHostConfig.js)\n+* [React ART](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-art\/src\/ReactART.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-art\/src\/ReactARTHostConfig.js)\n+* [React DOM](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-dom\/src\/client\/ReactDOM.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-dom\/src\/client\/ReactDOMHostConfig.js)\n+* [React Native](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-native-renderer\/src\/ReactNativeRenderer.js) and its [host config](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-native-renderer\/src\/ReactNativeHostConfig.js)\n \n If these links break please file an issue and we’ll fix them. They intentionally link to the latest versions since the API is still evolving. If you have more questions please file an issue and we’ll try to help!\n \n@@ -332,10 +332,10 @@ This method should mutate the `container` root node and remove all children from\n \n ### Persistence Methods\n \n-If you use the persistent mode instead of the mutation mode, you would still need the \"Core Methods\". However, instead of the Mutation Methods above you will implement a different set of methods that performs cloning nodes and replacing them at the root level. You can find a list of them in the \"Persistence\" section [listed in this file](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). File an issue if you need help.\n+If you use the persistent mode instead of the mutation mode, you would still need the \"Core Methods\". However, instead of the Mutation Methods above you will implement a different set of methods that performs cloning nodes and replacing them at the root level. You can find a list of them in the \"Persistence\" section [listed in this file](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). File an issue if you need help.\n \n ### Hydration Methods\n \n You can optionally implement hydration to \"attach\" to the existing tree during the initial render instead of creating it from scratch. For example, the DOM renderer uses this to attach to an HTML markup.\n \n-To support hydration, you need to declare `supportsHydration: true` and then implement the methods in the \"Hydration\" section [listed in this file](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). File an issue if you need help.\n+To support hydration, you need to declare `supportsHydration: true` and then implement the methods in the \"Hydration\" section [listed in this file](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-reconciler\/src\/forks\/ReactFiberHostConfig.custom.js). File an issue if you need help.\ndiff --git a\/packages\/react\/index.js b\/packages\/react\/index.js\nindex 247d17ec01..890b060847 100644\n--- a\/packages\/react\/index.js\n+++ b\/packages\/react\/index.js\n@@ -7,7 +7,7 @@\n * @flow\n *\/\n \n-\/\/ Keep in sync with https:\/\/github.com\/facebook\/flow\/blob\/master\/lib\/react.js\n+\/\/ Keep in sync with https:\/\/github.com\/facebook\/flow\/blob\/main\/lib\/react.js\n export type StatelessFunctionalComponent<\n P,\n > = React$StatelessFunctionalComponent
;\ndiff --git a\/packages\/use-subscription\/README.md b\/packages\/use-subscription\/README.md\nindex 549230211c..4ea34e1bca 100644\n--- a\/packages\/use-subscription\/README.md\n+++ b\/packages\/use-subscription\/README.md\n@@ -8,7 +8,7 @@ This utility can be used for subscriptions to a single value that are typically\n \n Most other cases have **better long-term solutions**:\n * Redux\/Flux stores should use the [context API](https:\/\/reactjs.org\/docs\/context.html) instead.\n-* I\/O subscriptions (e.g. notifications) that update infrequently should use a mechanism like [`react-cache`](https:\/\/github.com\/facebook\/react\/blob\/master\/packages\/react-cache\/README.md) instead.\n+* I\/O subscriptions (e.g. notifications) that update infrequently should use a mechanism like [`react-cache`](https:\/\/github.com\/facebook\/react\/blob\/main\/packages\/react-cache\/README.md) instead.\n * Complex libraries like Relay\/Apollo should manage subscriptions manually with the same techniques which this library uses under the hood (as referenced [here](https:\/\/gist.github.com\/bvaughn\/d569177d70b50b58bff69c3c4a5353f3)) in a way that is most optimized for their library usage.\n \n ## Limitations in concurrent mode\ndiff --git a\/scripts\/bench\/README.md b\/scripts\/bench\/README.md\nindex 2d1ea7bea3..ae567fa516 100644\n--- a\/scripts\/bench\/README.md\n+++ b\/scripts\/bench\/README.md\n@@ -27,8 +27,8 @@ yarn start --local\n # will only build and run remote merge base repo against benchmarks (no local values will be shown)\n yarn start --remote\n \n-# will only build and run remote master repo against benchmarks\n-yarn start --remote=master\n+# will only build and run remote main repo against benchmarks\n+yarn start --remote=main\n \n # same as \"yarn start\"\n yarn start --remote --local\ndiff --git a\/scripts\/bench\/build.js b\/scripts\/bench\/build.js\nindex 3ef0ffe186..9147d8519e 100644\n--- a\/scripts\/bench\/build.js\n+++ b\/scripts\/bench\/build.js\n@@ -55,7 +55,7 @@ async function getMergeBaseFromLocalGitRepo(localRepo) {\n return await Git.Merge.base(\n repo,\n await repo.getHeadCommit(),\n- await repo.getBranchCommit('master')\n+ await repo.getBranchCommit('main')\n );\n }\n \n@@ -82,15 +82,15 @@ async function buildBenchmarkBundlesFromGitRepo(\n \/\/ if not, clone the repo to remote-repo folder\n repo = await Git.Clone(url, remoteRepoDir);\n }\n- let commit = await repo.getBranchCommit('master');\n+ let commit = await repo.getBranchCommit('main');\n \/\/ reset hard to this remote head\n await Git.Reset.reset(repo, commit, Git.Reset.TYPE.HARD);\n- \/\/ then we checkout the latest master head\n- await repo.checkoutBranch('master');\n+ \/\/ then we checkout the latest main head\n+ await repo.checkoutBranch('main');\n \/\/ make sure we pull in the latest changes\n- await repo.mergeBranches('master', 'origin\/master');\n+ await repo.mergeBranches('main', 'origin\/main');\n \/\/ then we check if we need to move the HEAD to the merge base\n- if (commitId && commitId !== 'master') {\n+ if (commitId && commitId !== 'main') {\n \/\/ as the commitId probably came from our local repo\n \/\/ we use it to lookup the right commit in our remote repo\n commit = await Git.Commit.lookup(repo, commitId);\ndiff --git a\/scripts\/bench\/runner.js b\/scripts\/bench\/runner.js\nindex ce4e411063..922e914d4e 100644\n--- a\/scripts\/bench\/runner.js\n+++ b\/scripts\/bench\/runner.js\n@@ -61,7 +61,7 @@ async function runBenchmarks(reactPath) {\n }\n \n \/\/ get the performance benchmark results\n-\/\/ from remote master (default React repo)\n+\/\/ from remote main (default React repo)\n async function benchmarkRemoteMaster() {\n console.log(chalk.gray(`- Building React bundles...`));\n let commit = argv.remote;\ndiff --git a\/scripts\/error-codes\/README.md b\/scripts\/error-codes\/README.md\nindex 7d0988660f..9933e9903d 100644\n--- a\/scripts\/error-codes\/README.md\n+++ b\/scripts\/error-codes\/README.md\n@@ -2,14 +2,14 @@ The error code system substitutes React's error messages with error IDs to\n provide a better debugging support in production. Check out the blog post\n [here](https:\/\/reactjs.org\/blog\/2016\/07\/11\/introducing-reacts-error-code-system.html).\n \n-- [`codes.json`](https:\/\/github.com\/facebook\/react\/blob\/master\/scripts\/error-codes\/codes.json)\n+- [`codes.json`](https:\/\/github.com\/facebook\/react\/blob\/main\/scripts\/error-codes\/codes.json)\n contains the mapping from IDs to error messages. This file is generated by the\n Gulp plugin and is used by both the Babel plugin and the error decoder page in\n our documentation. This file is append-only, which means an existing code in\n the file will never be changed\/removed.\n-- [`extract-errors.js`](https:\/\/github.com\/facebook\/react\/blob\/master\/scripts\/error-codes\/extract-errors.js)\n+- [`extract-errors.js`](https:\/\/github.com\/facebook\/react\/blob\/main\/scripts\/error-codes\/extract-errors.js)\n is an node script that traverses our codebase and updates `codes.json`. You\n can test it by running `yarn extract-errors`.\n-- [`transform-error-messages`](https:\/\/github.com\/facebook\/react\/blob\/master\/scripts\/error-codes\/transform-error-messages.js)\n+- [`transform-error-messages`](https:\/\/github.com\/facebook\/react\/blob\/main\/scripts\/error-codes\/transform-error-messages.js)\n is a Babel pass that rewrites error messages to IDs for a production\n (minified) build.\ndiff --git a\/scripts\/error-codes\/extract-errors.js b\/scripts\/error-codes\/extract-errors.js\nindex 58823cbe16..4541a3eeea 100644\n--- a\/scripts\/error-codes\/extract-errors.js\n+++ b\/scripts\/error-codes\/extract-errors.js\n@@ -18,7 +18,7 @@ const babylonOptions = {\n \/\/ As a parser, babylon has its own options and we can't directly\n \/\/ import\/require a babel preset. It should be kept **the same** as\n \/\/ the `babel-plugin-syntax-*` ones specified in\n- \/\/ https:\/\/github.com\/facebook\/fbjs\/blob\/master\/packages\/babel-preset-fbjs\/configure.js\n+ \/\/ https:\/\/github.com\/facebook\/fbjs\/blob\/main\/packages\/babel-preset-fbjs\/configure.js\n plugins: [\n 'classProperties',\n 'flow',\ndiff --git a\/scripts\/merge-fork\/README.md b\/scripts\/merge-fork\/README.md\nindex 75208a5781..2b01bfe156 100644\n--- a\/scripts\/merge-fork\/README.md\n+++ b\/scripts\/merge-fork\/README.md\n@@ -51,7 +51,7 @@ By default, the changes are compared to HEAD. You can use `--base-ref` to compar\n \n ```sh\n yarn merge-fork \\\n- --base-ref=$(git merge-base HEAD origin\/master)\n+ --base-ref=$(git merge-base HEAD origin\/main)\n --base-dir=packages\/react-reconciler\/src \\\n ReactFiberWorkLoop\n ```\ndiff --git a\/scripts\/print-warnings\/print-warnings.js b\/scripts\/print-warnings\/print-warnings.js\nindex 9bdd6543d2..95dabcc1e1 100644\n--- a\/scripts\/print-warnings\/print-warnings.js\n+++ b\/scripts\/print-warnings\/print-warnings.js\n@@ -19,7 +19,7 @@ const parserOptions = {\n \/\/ babelParser has its own options and we can't directly\n \/\/ import\/require a babel preset. It should be kept **the same** as\n \/\/ the `babel-plugin-syntax-*` ones specified in\n- \/\/ https:\/\/github.com\/facebook\/fbjs\/blob\/master\/packages\/babel-preset-fbjs\/configure.js\n+ \/\/ https:\/\/github.com\/facebook\/fbjs\/blob\/main\/packages\/babel-preset-fbjs\/configure.js\n plugins: [\n 'classProperties',\n 'flow',\ndiff --git a\/scripts\/release\/README.md b\/scripts\/release\/README.md\nindex 979062dd14..1737c3cf18 100644\n--- a\/scripts\/release\/README.md\n+++ b\/scripts\/release\/README.md\n@@ -50,7 +50,7 @@ The sections below include meaningful `--tags` in the instructions. However, kee\n \"Next\" builds are meant to be lightweight and published often. In most cases, they can be published using artifacts built by Circle CI.\n \n To prepare a build for a particular commit:\n-1. Choose a commit from [the commit log](https:\/\/github.com\/facebook\/react\/commits\/master).\n+1. Choose a commit from [the commit log](https:\/\/github.com\/facebook\/react\/commits\/main).\n 2. Copy the SHA (by clicking the 📋 button)\n 5. Run the [`prepare-release-from-ci`](#prepare-release-from-ci) script with the SHA ^{1<\/sup> you found:\n ```sh\n@@ -115,7 +115,7 @@ Begin by creating a branch from the previous git tag^{1<\/sup>:\n git checkout -b 16.8.3 v16.8.2\n ```\n \n-Next cherry pick any changes from master that you want to include in the release:\n+Next cherry pick any changes from main that you want to include in the release:\n \n ```sh\n git cherry-pick \ndiff --git a\/scripts\/release\/prepare-release-from-ci.js b\/scripts\/release\/prepare-release-from-ci.js\nindex c61b3ed637..80dd051930 100755\n--- a\/scripts\/release\/prepare-release-from-ci.js\n+++ b\/scripts\/release\/prepare-release-from-ci.js\n@@ -12,7 +12,7 @@ const testPackagingFixture = require('.\/shared-commands\/test-packaging-fixture')\n \n const run = async () => {\n try {\n- addDefaultParamValue(null, '--commit', 'master');\n+ addDefaultParamValue(null, '--commit', 'main');\n \n const params = await parseParams();\n params.cwd = join(__dirname, '..', '..');\ndiff --git a\/scripts\/release\/prepare-release-from-npm-commands\/guess-stable-version-numbers.js b\/scripts\/release\/prepare-release-from-npm-commands\/guess-stable-version-numbers.js\nindex 1e9b560faf..a3cde5d1c4 100644\n--- a\/scripts\/release\/prepare-release-from-npm-commands\/guess-stable-version-numbers.js\n+++ b\/scripts\/release\/prepare-release-from-npm-commands\/guess-stable-version-numbers.js\n@@ -25,9 +25,9 @@ const run = async ({cwd, packages, skipPackages}, versionsMap) => {\n \n \/\/ Guess the next version by incrementing patch.\n \/\/ The script will confirm this later.\n- \/\/ By default, new releases from masters should increment the minor version number,\n+ \/\/ By default, new releases from mains should increment the minor version number,\n \/\/ and patch releases should be done from branches.\n- if (branch === 'master') {\n+ if (branch === 'main') {\n versionsMap.set(packageName, `${major}.${minor + 1}.0`);\n } else {\n versionsMap.set(packageName, `${major}.${minor}.${patch + 1}`);\ndiff --git a\/scripts\/release\/publish-using-ci-workflow.js b\/scripts\/release\/publish-using-ci-workflow.js\nindex 0bb6c7d0d6..48a834ba1f 100644\n--- a\/scripts\/release\/publish-using-ci-workflow.js\n+++ b\/scripts\/release\/publish-using-ci-workflow.js\n@@ -78,7 +78,7 @@ async function pollUntilWorkflowFinishes(workflowID) {\n \n async function main() {\n const headCommitResponse = await fetch(\n- 'https:\/\/api.github.com\/repos\/facebook\/react\/commits\/master'\n+ 'https:\/\/api.github.com\/repos\/facebook\/react\/commits\/main'\n );\n const headCommitJSON = await headCommitResponse.json();\n const headCommitSha = headCommitJSON.sha;\ndiff --git a\/scripts\/shared\/listChangedFiles.js b\/scripts\/shared\/listChangedFiles.js\nindex e9b586aa94..9db4e15071 100644\n--- a\/scripts\/shared\/listChangedFiles.js\n+++ b\/scripts\/shared\/listChangedFiles.js\n@@ -26,7 +26,7 @@ const execGitCmd = args =>\n .split('\\n');\n \n const listChangedFiles = () => {\n- const mergeBase = execGitCmd(['merge-base', 'HEAD', 'master']);\n+ const mergeBase = execGitCmd(['merge-base', 'HEAD', 'main']);\n return new Set([\n ...execGitCmd(['diff', '--name-only', '--diff-filter=ACMRTUB', mergeBase]),\n ...execGitCmd(['ls-files', '--others', '--exclude-standard']),\n","parents":["cae635054e17a6f107a39d328649137b83f25972"],"commit":{"revision":"d483463bc86555decb3e8caa18459d1d0f7c0148","subject":"Updated scripts and config to replace \"master\" with \"main\" branch (#21768)","authorName":"Brian Vaughn","authoredAt":"2021-06-29T14:26:24-04:00","shortRevision":"d483463bc8","authorEmail":"bvaughn@fb.com"},"body":""}}}

dillon1000/react

Files changed