Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR fixes critical issues with the React DevTools shell development environment that were preventing contributors from working on UI improvements and testing changes locally.
Problem: The DevTools shell was attempting to resolve React and related packages from a local build directory (build/oss-experimental), which caused module resolution errors and prevented the shell from running unless a full React build was present. This blocked UI development and local testing.
Solution:
Updated packages/react-devtools-shell/package.json to include react, react-dom, and react-is as direct dependencies
Modified packages/react-devtools-shell/webpack-server.js to resolve React packages from node_modules (npm versions) instead of the non-existent local build directory
This allows developers to run the DevTools shell immediately after yarn install without needing to build React from source
How did you test this change?
1. Forked repository and created branch from main
git checkout -b fix-devtools-shell-dependencies
2. Ran yarn in repository root
yarn install
3. Installed dependencies in DevTools shell package
cd packages/react-devtools-shell
yarn install