allow .ts for package exports #10495
Draft
+429
−298
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
refs: #5760
Description
#10480 tries
.ts
for contracts, which are not part of a package's export surface.This spike explores using
.ts
files for modules that are exported from a package. A complication is that while Typescript 5.7 can automatically convert rewrite.ts
to.js
in its build output, we've so far avoided having a build stage during development. So we need a way to have.ts
locally during development (without building) and for the packages in NPM to have only.js
files.Security Considerations
Scaling Considerations
Documentation Considerations
Testing Considerations
Upgrade Considerations