[DevTools] Check in frontend.d.ts
for react-devtools-fusebox, include in build output
#28970
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
The
react-devtools-fusebox
private package is used in the React Native DevTools (Fusebox) frontend by checking build artifacts into RN's fork of the Chrome DevTools (CDT) repo - see facebookexperimental/rn-chrome-devtools-frontend#22.Currently, the CDT fork also includes a manually written TypeScript definition file which describes
react-devtools-fusebox
's API. This PR moves that file into the React repo, next to the implementation ofreact-devtools-fusebox
, so we can update it atomically with changes to the package.As this is the first bit of TypeScript in this repo, the PR adds minimal support for formatting
.d.ts
files with Prettier. It also opts outreact-devtools-fusebox/dist/
from linting/formatting as a drive-by fix.For now, we'll just maintain the
.d.ts
file manually, but we could consider leveragingflow-api-translator
to auto-generate it in the future.How did you test this change?
Build
react-devtools-fusebox
, observe thatdist/frontend.d.ts
exists.