-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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.
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
TypeScript 5.2 Iteration Plan #54298
Comments
The previous Iteration Plan for TypeScript 5.1 is available here. |
Are there any plans or discussions regarding #53656? |
Also interested if you have any plans regarding #41316? Working on libraries seems impossible without it sometimes. |
@typescript-bot sync release-5.2 and LKG |
Heya @DanielRosenwasser, I've started to sync |
@Mike-Dax my PR isn't (yet) complete - it has some rough edges that I need to figure out. I'd happily collaborate on this one with somebody, I already know what I want to do there just need to find a proper way to fit those ideas into the code and the available data structures. |
What the… what even kind of bot is this |
Not explicitly mentioned above but this also lands support for Change Array By Copy methods (eg Issue: #50333 |
FYI: #54923 |
@typescript-bot bump release-5.2 |
Heya @DanielRosenwasser, I've started to update the version number on |
How template literals as computed properties on objects are now typed as literals instead of strings seems to not be mentioned in the changelog: const key = 'foo'
// {
// foo: number;
// "foo-de": string;
// }
const object = {
[key]: 1,
[`${key}-de`]: "2"
}
// Errors in 5.1.6 with "Property 'match' does not exist on type 'string | number'."
object['foo-de'].match(/2/)
object['foo'] + 1; vs const key = 'foo'
// {
// [x: string]: string | number;
// foo: number;
// }
const object = {
[key]: 1,
[`${key}-de`]: "2"
}
// @ts-expect-error
object['foo-de'].match(/2/)
object['foo'] + 1; Seems like a good change but probably worth mentioning. |
If im not mistaken this was changed by #53907 |
Also positive change: referencing const enums in template literal types used to error under export declare const enum OBJECT_INDICATION_TYPE {
HIGHLIGHTED_DOT = "HIGHLIGHTED_DOT"
}
type Values<T> = {
[K in keyof T]: T[K];
}[keyof T];
export type IndicationType = `${Values<typeof OBJECT_INDICATION_TYPE>}`;
// Fixed: ^^^^^^^^^^^^^^^^^^^^^^ Cannot access ambient const enums when 'isolatedModules' is enabled.(274
export {}; |
@typescript-bot bump release-5.2 |
Heya @DanielRosenwasser, I've started to update the version number on |
Version 5.2.2 is already available on npm, but I don't see a corresponding tag and release/changelog in this repository. Can you add the actual release here on the github? |
It's tagged now - but can I ask what you all use the tag for? |
Speaking for myself: Github watch notifications on release tags to know when new releases happen. |
— Release notifications / changelogs |
I've upgraded to 5.2.2 but still shows error. |
@RHOOPH I think your runtime (whether browser or Node) still needs to use Node v20 is the first Node version to support it, for example. Scroll down to that line in this compatibility chart: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array#browser_compatibility |
target should set to esnext. In tsconfig.json |
This document outlines our focused tasks for TypeScript 5.2. It minimally indicates intent to investigate tasks or contribute to an implementation. Nothing is set in stone, but we will strive to complete these tasks in a reasonable timeframe.
Compiler and Language
using
DeclarationsArray
method signature mergingtsc
lib.d.ts
UpdatesEditor and Language Service
type
ImportsPerformance
.tsbuildinfo
Website and Docs
Infrastructure
The text was updated successfully, but these errors were encountered: