fix: types for module resolution bundler - #835
Conversation
... as it overrides each `exports` element's type field and does not seem to be necessary
... as it overrides each `exports` element's type field and does not seem to be necessary
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
🦋 Changeset detectedLatest commit: d696fde The changes in this PR will be included in the next version bump. This PR includes changesets to release 12 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
◈ PR Lens
Architecture 16 components touched across 7 lanes. Data flow No data-flow sequence changed in this PR. Drill down
|
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🎯 Changes
Added explicit
typesparam for eachexportsfield in package.json files, so that they can be used by "modern" bundlers (which do not read the "legacy" top-leveltypesfield).Disabled tsdown's automatic
exportsgeneration, as it does not support export-specifictypesand thus keeps overwriting the previously mentioned changes.✅ Checklist
pnpm run test.🚀 Release Impact