Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Comments

chore: enable tsdown auto-generated package exports#2924

Merged
melloware merged 5 commits intoorval-labs:masterfrom
froggy1014:chore/tsdown-auto-exports
Feb 8, 2026
Merged

chore: enable tsdown auto-generated package exports#2924
melloware merged 5 commits intoorval-labs:masterfrom
froggy1014:chore/tsdown-auto-exports

Conversation

@froggy1014
Copy link
Contributor

Summary

  • Enable exports: true in tsdown base config to auto-generate exports, main, module, types fields in package.json
  • Normalize all package exports from manual nested conditions to tsdown-managed format
  • Fixes incorrect exports structure (missing "." subpath) in some packages

Motivation

Previously, each package manually defined exports with inconsistent formats — some used nested import.types conditions, others used flat strings. With tsdown's exports option, these fields are auto-generated on build, ensuring consistency across all packages and reducing manual maintenance.

Reference

@melloware
Copy link
Collaborator

@froggy1014 can you check if this fixes this? #2912 I saw your mention of incorrect export path

@melloware melloware added this to the 8.3.0 milestone Feb 8, 2026
@froggy1014
Copy link
Contributor Author

@froggy1014 can you check if this fixes this? #2912 I saw your mention of incorrect export path

@melloware

This PR only changes the package-level exports field in each package.json for bundling.
it doesn't affect the generated client code at all.

#2912 is about incorrect import paths in the generated output when indexFiles: false, which is a separate code-gen issue. This PR won't fix that.

@melloware melloware merged commit f317f8b into orval-labs:master Feb 8, 2026
2 checks passed
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