Skip to content

Issues: microsoft/TypeScript

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clear current search query, filters, and sorts
22 Open 408 Closed
22 Open 408 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Always treat .d.*.ts files as commonjs-format modules for the purposes of import interop Author: Team Breaking Change Would introduce errors in existing code Domain: ES Modules The issue relates to import/export style module behavior For Milestone Bug PRs that fix a bug with a specific milestone
#59622 opened Aug 13, 2024 by weswigham Loading…
1
@weswigham
1
Always resolve package.json exports in type reference directives Author: Team Breaking Change Would introduce errors in existing code For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
#58638 opened May 23, 2024 by andrewbranch • Draft
1
@andrewbranch
19
.d.json.ts file (allowArbitraryExtensions) not working correctly when importing from ESM file with node16/nodenext module setting Breaking Change Would introduce errors in existing code Bug A bug in TypeScript Fix Available A PR has been opened for this issue Rescheduled This issue was previously scheduled to an earlier milestone
#57229 opened Jan 30, 2024 by noinkling TypeScript 5.7.0
1
@weswigham
4
Do not erase signature constraints when calculating variance Author: Team Breaking Change Would introduce errors in existing code Experiment A fork with an experimental idea which might not make it into master For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
#55864 opened Sep 25, 2023 by weswigham • Draft
1
@weswigham
14
Infer unknown at value positions of objects inferred from keyof T Breaking Change Would introduce errors in existing code For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
#55547 opened Aug 28, 2023 by Andarist Loading…
@DanielRosenwasser
27
Do not widen computed properties with template literal types Breaking Change Would introduce errors in existing code For Uncommitted Bug PR for untriaged, rejected, closed or missing bug
#54706 opened Jun 19, 2023 by Andarist Loading…
@weswigham
8
Always look for tsconfig, allow command line to override tsconfig file list Author: Team Breaking Change Would introduce errors in existing code For Uncommitted Bug PR for untriaged, rejected, closed or missing bug Rescheduled This issue was previously scheduled to an earlier milestone
#49817 opened Jul 6, 2022 by weswigham • Draft TypeScript 5.5.5
1
@weswigham
6
Enum with special numbers overwrites own value Breaking Change Would introduce errors in existing code Bug A bug in TypeScript
#48956 opened May 4, 2022 by JacobLey TypeScript 5.4.0
1
4
Inconsistent parameter properties initialization order depending on the target syntax with useDefineForClassFields Breaking Change Would introduce errors in existing code Domain: JS Emit The issue relates to the emission of JavaScript Rescheduled This issue was previously scheduled to an earlier milestone
#45995 opened Sep 21, 2021 by nicolo-ribaudo TypeScript 5.7.0
@rbuckton
8
Symbol properties should not be exempt from excess property checks in presence of a string index signature Breaking Change Would introduce errors in existing code Bug A bug in TypeScript Fix Available A PR has been opened for this issue Rescheduled This issue was previously scheduled to an earlier milestone
#44794 opened Jun 28, 2021 by DanielRosenwasser TypeScript 5.7.0
1
@ahejlsberg
4
Cannot bracket-index into an object after checking it's existence on that object. Breaking Change Would introduce errors in existing code
#44117 opened May 17, 2021 by h-joo
@DanielRosenwasser
4
allowJs should default to true Breaking Change Would introduce errors in existing code Needs More Info The issue still hasn't been fully clarified Suggestion An idea for TypeScript
#40345 opened Sep 1, 2020 by sandersn Backlog
@sandersn
1
No error using imports/exports with --module=none and --target=es2015+ Breaking Change Would introduce errors in existing code Bug A bug in TypeScript Rescheduled This issue was previously scheduled to an earlier milestone
#39603 opened Jul 14, 2020 by andrewbranch Backlog
3
Change Diagnostic.code to 'string | number' API Relates to the public API for TypeScript Breaking Change Would introduce errors in existing code Experience Enhancement Noncontroversial enhancements Suggestion An idea for TypeScript
#28911 opened Dec 7, 2018 by ajafff Backlog
3
USVString type definition Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Breaking Change Would introduce errors in existing code Domain: lib.d.ts The issue relates to the different libraries shipped with TypeScript Suggestion An idea for TypeScript
#28775 opened Nov 30, 2018 by hasbel
7
Inserting intersections with 'Function' while narrowing breaks code Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Breaking Change Would introduce errors in existing code Suggestion An idea for TypeScript
#26970 opened Sep 7, 2018 by DanielRosenwasser
6
API: incorrect declarations in types.ts Breaking Change Would introduce errors in existing code Help Wanted You can do this Infrastructure Issue relates to TypeScript team infrastructure
#24706 opened Jun 5, 2018 by ajafff Backlog
5
Object.getPrototypeOf returns any instead of object | null Awaiting More Feedback This means we'd like to hear from more people who would be helped by this feature Breaking Change Would introduce errors in existing code Suggestion An idea for TypeScript
#22875 opened Mar 26, 2018 by cshaa
5
Decouple jsx element type from jsx factory return type and sfc return type Breaking Change Would introduce errors in existing code Domain: JSX/TSX Relates to the JSX parser and emitter Effort: Moderate Requires experience with the TypeScript codebase, but feasible. Harder than "Effort: Casual". Fix Available A PR has been opened for this issue Suggestion An idea for TypeScript
#21699 opened Feb 6, 2018 by weswigham Backlog
2
115
Try enforcing contextual type of array literal elements Breaking Change Would introduce errors in existing code Committed The team has roadmapped this issue Suggestion An idea for TypeScript
#19541 opened Oct 27, 2017 by RyanCavanaugh Backlog
2
Bug: Accessing private statics in a class via its derived class is allowed Breaking Change Would introduce errors in existing code Effort: Moderate Requires experience with the TypeScript codebase, but feasible. Harder than "Effort: Casual". Help Wanted You can do this Suggestion An idea for TypeScript
#8624 opened May 16, 2016 by JoshuaKGoldberg Backlog
22
Enum types are not checked in binary operators Breaking Change Would introduce errors in existing code Bug A bug in TypeScript Help Wanted You can do this
#3845 opened Jul 13, 2015 by JsonFreeman Backlog
5
ProTip! Adding no:label will show everything without a label.