Repository navigation
TypeScript 3.5 Iteration Plan #30555
Description
Activity
- pinned this issue
on Mar 23, 2019 Daniel Rosenwasser (@DanielRosenwasser) Thanks for being so transparent with the plans. It was way cool to read the 3.4 release announcement and then pop over here to see that you already have pretty developed plans for the next iteration.
Go TypeScript team!
Reacted by Bnaya Peretz, Veniamin Krol, Dmitrijs Minajevs, evelyn ♡, Haz, Donald Pipowitch, Kyle Bastien, Yaroslav Admin, Kon Pik, gmurray81 and 42 moreReacted by Daniel Rosenwasser, Borek Bernard, apalumbo, Teddy Cross, Jiri Spac, Bnaya Peretz, Rizky Luthfianto, Joseph Kohlmann, csha, Andrew Branch and 3 moreAmazing work guys!
Reacted by Jiri Spac and kissyjoyReacted by Daniel RosenwasserI’d like to see #30586 fixed.
Preferably in some way that isn’t just a band‑aid.
What's TypeScript plugin API? Does this affect babel-plugin-transform-typescript users?
Reacted by Brody McKeeIs it possible to be involved in testing for "Investigate TypeScript plugin APIs"?
I'd love to have
typescript-plugin-css-modulesavailable during build time. I'm currently in the process of reworking it a little, so please let me know.Reacted by Bnaya Peretz, ZHAO Jin-Xiang, ExE Boss, joan xie, Christian, Meirion Hughes, Syrotenko Igor, Christopher Boyd, Ádám Lippai, Bazyli Brzóska and 1 moreReacted by Syrotenko Igor, ZHAO Jin-Xiang and Bnaya PeretzI'd like to see #21592 fixed.
It force me to stuck with TypeScript 3.1.6 😢(the only version without this bug among TS 3.x)
Hey all, just wanted to put out a couple of updates. A few of the items in this release were reprioritized, and as a result, what you see in the current feature roadmap is the closest to what you'll see in the release next week.
There are a couple of reasons why, but most of it was that TypeScript 3.4 was rockier than expected, and so was some breakage in TypeScript 3.5 itself. We ended up spending a lot of time servicing the last release or chasing down regressions.
It turns out that our testing infrastructure, while improved, needs investment. Our testing suite isn't up to date on real world code, and doesn't test things like editor scenarios (e.g. keystroke delays when a library like styled-components is present). We need to do our due diligence to invest in this testing infrastructure and run it more frequently on major changes. We also want to make it easier to contribute repositories to TypeScript's code suite.
Another thing we've been feeling is that we as a language need to have more time to let features "bake". We may be moving towards 3-month release cycles to address stability issues and feel confident in our design decisions. We'd like to experiment with this release cycle to ensure that users get stable well-designed features without compromising the rapid iteration we've been able to provide.
Much of this will also be coming in TypeScript 3.6. Keep posted for the upcoming iteration plan.
Reacted by Gulshan, Demian Ferreiro, ExE Boss, Jordi Oliveras Rovira, Thibaud Giovannetti, Sam A. Horvath-Hunt, NtFreX, Johnatha Felix, Steven, Ryan Cavanaugh and 18 moreJust as one final heads up - due to personnel reasons, we'll be releasing tomorrow morning (the 29th) rather than Thursday the 30th. See you then!
Reacted by Jacek Karczmarczyk, Kelli Rockwell, ExE Boss, Bnaya Peretz, Titian Cernicova-Dragomir, Veniamin Krol, Andi Pätzold, cpoul, Steven, Thibaud Giovannetti and 2 moreWe did it!
Reacted by Daniel Rosenwasser, Wenlu Wang, Titian Cernicova-Dragomir, Veniamin Krol, Steven, Thibaud Giovannetti and YaojianReacted by Daniel Rosenwasser, Wenlu Wang, ExE Boss, Jessica Franco, Titian Cernicova-Dragomir, Veniamin Krol, Sam A. Horvath-Hunt and StevenReacted by Daniel Rosenwasser, Wenlu Wang, Veniamin Krol and Steven- unpinned this issue
on May 29, 2019 Why hasn't 3.5.x been released on GitHub? It's tagged as the latest on npm.
Reacted by Cry0nicS, ExE Boss and Jared M. Peterson
This document outlines our focused tasks for TypeScript 3.5, as well as some of the discussion that explains how/why we prioritized certain work items. Nothing is set in stone, but we will strive to complete them in a reasonable timeframe.
Dates
Here's the release plan.
release-3.5branch, and update the version to3.5.0-rc.masteris locked from receiving new feature-work that is not 3.5-bound.release-3.5branch with any feedback we receive.masterintorelease-3.5one last time, finalize the version as3.5.1.masteris unlocked. Critical changes for 3.5 must be ported in.release-3.5branch with any feedback we receive.Work Items
Expected Work Items
globalThisexpressivity fixes--incrementalfixes and improvements--declarationand--allowJs--declarationand--isolatedModules--incrementaland composite projects (--buildmode) 🏃(🏃🏻 means work has already started)
Deferred Work Items
Planning Meeting Notes
Motivations
General (compiler/infrastructure/reliability)
Negated types
Arbitrary index signatures
Compiler API prototyping
Expecting
--incrementalbuild issuesCrawler work for testing TSServer
TSLint -> ESLint migration
New engineer starting!
globalThis-related work--declarationwith--allowJs--declarationwith--isolatedModulescomposite.Productivity
<T>(x: T): { value: T }