temporalio / temporalio/documentation
Evaluate TypeScript bundler module resolution for package exports
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 173
- Forks
- 330
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 156
Description
Change the docs TypeScript configuration from moduleResolution: "node" to moduleResolution: "bundler" so TypeScript resolves package exports maps the same way the Docusaurus webpack build does.
This should allow public package subpath imports such as @temporalio-web/consent-banner/core to use the package's shipped type declarations directly, without local compatibility shims.
Scope:
- Update
tsconfig.jsonto usemoduleResolution: "bundler". - Remove
types/temporalio-web-consent-banner.d.tsif TypeScript resolves@temporalio-web/consent-banner/coredirectly. - Run
npx tsc --noEmit -p tsconfig.json. - Run
yarn buildto confirm Docusaurus still builds with the updated resolver assumptions. - Fix any package import errors exposed by stricter package
exportshandling.
Notes:
A quick static scan found no obvious unexported package deep imports. Existing package subpath imports appear to be exported by their packages, including Docusaurus client/internal entrypoints, Algolia, Chart.js, React Icons, DocSearch, and the Temporal consent banner core entrypoint.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tsconfig.json and inspect types/temporalio-web-consent-banner.d.ts and the documented package subpath imports. Run npx tsc --noEmit -p tsconfig.json, then yarn build; update the resolver configuration, remove the compatibility declaration only if direct resolution works, and fix any package import errors exposed by package exports handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system, documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100