You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 8b8c279
Browse filesBrowse the repository at this point in the historyBrowse files
## Why
The web libraries expose their declarations through `exports`.
TypeScript's legacy `node` resolver does not read that field, so hosts
using it cannot resolve the public imports without changing their
compiler configuration.
## Change
Add a top-level `types` entry and explicit `typesVersions` mappings for
the public JavaScript subpaths in platform, Stovepipe, and SubmitQueue.
Keep the existing exports, ESM output, and browser/server boundaries
unchanged. This adds declaration resolution support, not CommonJS
support.
Use the same packaged consumer fixture to check every public JavaScript
entry point with both `node` and `bundler` resolution. Run the new
legacy-resolver check in the normal web test suite.
## Test plan
- `make web-check` (includes both consumer typechecks, package contents,
Node runtime, and React 18 rendering checks)
- `make fmt`, `make lint`, `make check-tidy`, `make check-gazelle`
0 commit comments