Skip to content

fix: remove unused react-dom/client mapping from dnt build - #271

Merged
kwakayama merged 1 commit into
mainfrom
fix/dnt-unused-react-dom-client-mapping
Feb 9, 2026
Merged

kwakayama merged 1 commit into
mainfrom
fix/dnt-unused-react-dom-client-mapping

Conversation

@kwakayama

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • deno run -A scripts/build/build-npm-dnt.ts completes successfully
  • Pre-commit verification passes (fmt, lint, typecheck)

The API surface refactor (#264) reduced exports to 18 flat paths, none
of which transitively import react-dom/client. dnt fails when a mapping
is specified but no entry point source file references it.
Copilot AI review requested due to automatic review settings February 9, 2026 00:37
@kwakayama
kwakayama merged commit b8746d0 into main Feb 9, 2026
16 checks passed
@kwakayama
kwakayama deleted the fix/dnt-unused-react-dom-client-mapping branch February 9, 2026 00:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the npm packaging pipeline by removing an unnecessary react-dom/client esm.sh mapping from the dnt build script, aligning the mapping list with the current (reduced) public entrypoint module graph so dnt no longer errors on an unused mapping.

Changes:

  • Removed the https://esm.sh/react-dom@19.1.1/client?... → react-dom/client mapping from the dnt mappings config.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

ariskemper pushed a commit that referenced this pull request Feb 9, 2026
The API surface refactor (#264) reduced exports to 18 flat paths, none
of which transitively import react-dom/client. dnt fails when a mapping
is specified but no entry point source file references it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants