-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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.5 Iteration Plan #57475
Comments
How much of an impact will |
None directly, in the same way that But, if you have code which passes |
(This isn't to say that there can't be some speedups possible in TypeScript in the future enabled by this option, just that the flag itself is intended to just be checks.) |
Hey everyone, any chance of getting #26242 in this release? It was proposed back in 2018 and there has not been much work on the issue up to this point. Getting it at least planned would already be amazing to the TS community. I believe it would substantially improve the power of TS in the long run! |
Just a heads up, I'm working on remaking the website using Sveltekit. Styles will be the same, but the overall structure will be simpler and much quicker to iterate on. |
@ClearedFram3 while I don't want to discourage experimentation, I don't think we would accept such a large PR without discussing changes ahead of time. |
@DanielRosenwasser I should've said the codebase structure will be different—the website style/content structure will be the same. After the current codebase is replaced, there will ample room for discussion about changing design and content or even to a different framework haha. |
I’ve been watching the iteration plan threads from 5.4 seeing my PR (#55600) on the list. I am on standby anytime for any necessary alternations. |
Is there anything Typescript community members can do to influence this list? I think I can speak for every TS React dev on the planet when I say that #29526 (improved syntax for destructuring an argument ... like the React I can't speak for anyone else, but personally I would trade everything on the 5.5 list for this one feature! |
A question about Investigate Recursive Object Type References |
|
Is there any chance after 10 years.. to introduce nameof? Is it super complicated? Honest question |
@typescript-bot bump release-5.4 |
Hey, @DanielRosenwasser! I've set the version of release-5.4 to 5.4.4 for you. |
@typescript-bot bump release-5.4 |
Whoops - I've been posting in the wrong iteration plan. Sorry for the noise folks. |
Hey, @DanielRosenwasser! I've set the version of release-5.4 to 5.4.5 for you. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This is the first I am hearing about this.. (I guess I've had my head in the sand for a while).. We already have a solution to this.. This type of stuff is going to push the whole "Javascript can run TS script directly, but just ignoring the types" concept even FURTHER AWAY! |
Then why not add your voice to that issue? Respond to the arguments and examples presented there, there.
Again, if you join the actual discussion you can respond to people who are addressing this exact concern (#29526 (comment)). The only argument I see in that issue is that the double-colon syntax may actually benefit this cause. If there's an argument to the contrary, you should make it there so it can be properly considered. |
Most devs believe in the "DRY principle". When you use the syntax you mentioned, it's not DRY code; you have #29526 is simply about eliminating duplication, nothing more. There are already 30+ devs participating in that discussion (and who knows how many are lurking), all because they want to see that duplication eliminated. If you have something against eliminated duplication, by all means respond ... in that ticket. This thread is not the appropriate place to discuss any particular ticket. |
Hey, @DanielRosenwasser! I've set the version of release-5.5 to 5.5.1-rc for you. |
There will no Only |
Hey all, my apologies on the delays - that's mostly on me, but as always, I'll note that the schedule is aspirational and not a promise on exact dates.
|
The blog post is out for the RC, as is the git tag |
The RC got pushed back 2 days (June 6th) (typical) so the stable release will go out 2 days later (June 20th) (typical). |
@typescript-bot bump release-5.5 |
Hey, @DanielRosenwasser! I've set the version of release-5.5 to 5.5.2 for you. |
Property 'once' does not exist on type 'EventEmitter'. Did you mean to access the static member 'EventEmitter.once' instead? I am get this error after update to 5.5.2? My code has not change. How fix? |
Pls fix |
@Anonymous4078 if you are having problems and you believe you're hitting a bug, please file a separate issue. Otherwise, if you just have an upgrade question, try asking on StackOverflow or on our Discord chat. |
Was 5.5.2 withdrawn? |
@HolgerJeromin yes, there was an issue with the NuGet package due to changes in the internal layout for TypeScript. @joj and others are investigating that. |
@DanielRosenwasser What is the status of the LSP support in this release? I see it in the iteration plan to "define an initial sketch" but there's nothing about it in the release notes. Are we any closer to getting it? |
These iteration plans are only a prospective list; in this case I had other critical work that preempted me working on anything tangible for LSP. What use case do you have where LSP would be valuable? |
@jakebailey We met with Daniel a few months ago to discuss our project. It's a TypeScript-based DSL with a custom file extension for which we need to implement our own VS Code extension. Our DSL is a subset of TypeScript so we need to disallow certain things and provide custom completions, etc. We implemented some of this as a It is possible to load a Our options are thus: (A) Fork the internal |
I don't really see how LSP would help that situation; LSP will within reason only change the way tsserver talks to the editor. It'd still be the same In any case, I think this is the wrong place to discuss it (pinging everyone interested in the 5.5 release process); the update is just that "I didn't have time to work on it". The current LSP thinking is to slowly onboard calls away from the old protocol onto the new one, so it's not going to be like one day we aren't LSP and one day we are, either. |
@typescript-bot bump release-5.5 and LKG |
Hey, @DanielRosenwasser! I've set the version of release-5.5 to 5.5.3 for you. |
5.5.3 is out with the NuGet/VS issues fixed. Thanks for your patience everyone! |
Will #26242 be implemented in the next version, as it is so important to library developers? |
@typescript-bot bump release-5.5 and LKG |
Hey, @DanielRosenwasser! I've set the version of release-5.5 to 5.5.4 for you. |
This document outlines our focused tasks for TypeScript 5.5. 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
--isolatedDeclarations
Flagtsconfig.json
Filesdefault
Import Interop Configurabilitydefault
Import Detection from ECMAScript ModulesSet
Methodslib.d.ts
UpdatesEditor and Language Service
Performance
--incremental
ModeWebsite and Docs
Infrastructure
--isolatedDeclarations
and Parallelize TypeScript's BuildThe text was updated successfully, but these errors were encountered: