-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Support isWellFormed
and toWellFormed
in lib.esnext.d.ts
#55543
Comments
How do these types require support by the TypeScript compiler? Sounds to me that it just needs updated |
Because even with |
isWellFormed and toWellFormed are ES features, so they belong in the lib defs, not |
isWellFormed
and toWellFormed
in lib.esnext.d.ts
AFAIK these should be added to |
I think usually we don't create a new target/library combo until the spec edition is ratified. I think |
Ah, I missed that https://tc39.es/ecma262/ shows the draft state. Is there a handy link that shows all spec versions and their statuses? |
@andrewbranch https://github.com/tc39/ecma262/releases Every release is cut at around April–June, and new features are always mentioned in the introduction. |
These two methods are part of the well-formed Unicode strings proposal (https://github.com/tc39/proposal-is-usv-string), which reached stage 4 in May 2023 and will be part of ES2024. Fixes microsoft#55543.
🔍 Search Terms
NodeJS 20, isWellFormed, toWellFormed
✅ Viability Checklist
⭐ Suggestion
NodeJS 20 introduces new features that are not supported by the TypeScript compiler yet.
As an example node version 20 introduces
String.prototype.isWellFormed
andString.prototype.toWellFormed
. Using these functions causeserror TS2339: Property 'isWellFormed' does not exist on type 'string'.
Current environment:
📃 Motivating Example
This update will enable developers to fully use all features available in the latest major version of NodeJS.
💻 Use Cases
This would allow the usage of ECMAScript features such as
isWellFormed
andtoWellFormed
.The only current workaround is to use
// @ts-ignore
to let the project compile.The text was updated successfully, but these errors were encountered: