Skip to content

Conversation

andrewbranch
Copy link
Member

No description provided.

however, only TypeScript-specific syntax that does not have runtime semantics are supported under this mode.
In other words, it must be possible to easily *erase* any TypeScript-specific syntax from a file, leaving behind a valid JavaScript file.

That means the following constructs are not supported:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might want to wait to merge this until microsoft/TypeScript#61244 (which I believe we're going to talk about in a meeting soon).

Copy link
Member

@jakebailey jakebailey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In any case, seems fine. I don't know if we merge the blog post to the website before actual release (but I also don't know when you were planning on merging)

@andrewbranch
Copy link
Member Author

I’m fine to wait until the release. Just getting ready, because I put some anchor links in SchemaStore/schemastore#4503 that don’t exist yet.

@andrewbranch andrewbranch merged commit 71aa8ee into v2 Feb 28, 2025
8 checks passed
@andrewbranch andrewbranch deleted the 5.8 branch February 28, 2025 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants