microsoft / microsoft/TypeScript
export default type
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
Search Terms
export default type
Suggestion
Allow export default for type.
Use Cases
It would be very nice to have export default type to match with other default exports such as classes and interfaces.
Right now it looks very inconsistent to be able to export anything as default and only types with named export:
export default class MyClass {}
export default interface MyInterface {}
export type MyType = {}
The only way to achieve this now is to use annoying workaround:
type X = number | string
export { X as default }
This may cause confusion for newbies as there are no clear reasons why classes and interfaces can be exported as default, but not the types.
Examples
// x.ts
export default type X = {}
// main.ts
import X from './x'
Checklist
My suggestion meets these guidelines:
- This wouldn't be a breaking change in existing TypeScript/JavaScript code
- This wouldn't change the runtime behavior of existing JavaScript code
- This could be implemented without emitting different JS based on the types of the expressions
- This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
- This feature would agree with the rest of TypeScript's Design Goals.
(not sure on the last)
Contributor guide
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
The issue provides syntax examples for adding default exports to types but names no source files, tests, or entry points. Start by tracing existing handling of default class and interface exports, then determine the parser, checker, and emit behavior that would need coverage; done means the proposed syntax works with the shown import without changing emitted JavaScript.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100