TypeScript Roadmap: July - December 2019 #33118
Comments
|
Looking forward to the pipeline op very much. :XD |
The TSConf website doesn't really say much about what it really is. Is there anything else? =P |
|
@AnyhowStep that's usually what conferences are, bunch of talks, people talking, people networking, people plotting the overthrow of Javascript and its replacement with Typescript by violent revolution.... Um.. Have I said too much? |
|
|
I would like to ask if there is any planned advancement on allowing custom Transformers via the |
|
In light of the focus on more expressiveness in the type system, and the recent changes to setters/getters in type declarations, might I propose that this issue is given another look? I think improving this would allow for more accurate description of the actual types of existing JS libraries as they stand, not to mention the DOM's actual behavior. |
❤️ |
|
@jack-williams The FAQ is an interesting one, I wonder if it can be expanded into a section (with sub-sections) in the new site because that wiki page is redonqulously big. Happy to chat about ideas on an issue in the website if you've got ideas (otherwise I'll put it on my back burner to think about) |
|
@orta Where should I move the discussion to? I don't know if I've got any good ideas, but maybe in the course of talking about it something will emerge. |
|
The website issues is a good spot for this https://github.com/microsoft/TypeScript-website/issues |
|
Cheers! That's what I thought you meant, but I was being slow. |
|
Have you guys set a target release for optional chaining now that its reached Stage 3? |
|
#16 is going to change lives. The |
|
It is about time to support last arguments and elements #1360. |
|
Technically the FAQ can be edited on https://github.com/Microsoft/TypeScript-wiki/ |
|
I hope I live to see that day when Typescript will have |
|
What's protocols? Is this one? |
Are there any existed issues? I'm very interested in this one. |
|
Add a tsc flag to translate import paths to relative ones in the compiler output, please! Thousands of developers are waiting for this feature and have to use fragile hacks through ttypescript/plugins or cheat with NODE_PATH env variable. #15479 - marked as “out of scope”, although it deserves one more look. |
|
@DanielRosenwasser O MY GOD! |
|
I found some Types on my desk |
|
@dko-slapdash Not likely to happen, unfortunately: #31643 (comment) |
|
Hello TS Team! I appreciate your efforts to improve typescript performance! I'm very happy using TS, but as my project (react native) grew performance started to fall so badly, that it's the biggest factor impacting my productivity. I have to reset TS server ~every 30 minutes (I'm using VS Code), quite frequently more often than that. Autocomplete with auto-import often works in a weird way - it properly suggests a variable name, but when I use it - it's not importing needed module. Sometimes I have to CMD+Space to see import suggestions, but sometimes it does not work and I have to manually write imports. Often autosuggestions start to work so slowly (3-10s) that it becomes unusable. I'd like to help you by providing some feedback, but I actually don't know how to collect needed data. I've tried to enable verbose logs, but I'm getting a huge amount of logs (often more than 50mb) which includes so much noise, that I actually have no idea what is going on. It would be very useful to have some sort of guide related to actually detecting and narrowing down issues with the ts server. It would be awesome to have some 'smart' diagnostics tool that would be able to tell something like 'this module types took 80% of time needed for suggestions collection caused by your last CMD+space' I'm open to having some sessions with you trying to reproduce the issue. I don't have any specific scenario. Sometimes it works just fine for 2 hours after restarting TS server and sometimes I have to restart it every 10 minutes so I'm worried I'll waste your time if I'll not be able to reproduce it. If you're interested, however - I'd be more than happy to help as much as I can. Screen Recording 2020-04-02 at 10.44.43 PM.mov.zip I'm sending screen recording with issue - when I'm typing - it suggest proper variable name I can import, but when I use it - it's not actually imported. I have to CMD+Space at the end of it again to make VS Code suggest me to import given variable |
|
Please don't file issues as comments on the roadmap, folks. It makes it significantly harder for us to manage the issue tracker. Also, closing this as #36948 is the current active roadmap. |
Roadmap Overview
This roadmap is meant to give our team and users clarity over our priorities over the next 6 months. It's meant more as a set of guidelines than as a strict set of tasks we are bound to finish.
At a high-level, we're going to be focusing on the following 5 goals:
The how is broken down into the following sections:
If you've seen our last 6-month roadmap, you will notice that our goals and areas of investment haven't changed. The biggest change you might notice are specific work items and amount we'll be focusing on each area of investment. As an example, we're still committed to supporting editor scenarios, but right now we're more interested in ensuring that editor features are fast.
Language design and innovation
TypeScript and the core type system
This is a continuous and iterative process. The goal of TypeScript's type system is to statically model patterns in JavaScript in a reasonable way while catching bugs and enforcing correctness. As more features are added to ECMAScript, and as we notice emerging patterns in the ecosystem, we have more work to do, and because the JavaScript world moves fast, so must we.
While nothing has changed here, we have noticed any change we make may break existing code or hurt performance. We do not believe this should deter us from investment in these areas, but we will have to test more than before. More on this later in the document.
Back to top
JavaScript: TypeScript beyond TypeScript
TypeScript isn't just for TypeScript anymore. Our userbase now includes the JavaScript ecosystem as a whole, whether they are
.js/.jsxfiles in editors powered by TypeScript,allowJs.checkJs(also enabled by the// @ts-checkcomment), orWhoever these users are, we believe TypeScript can serve them in some way.
The majority of our investment here will likely be for editor scenarios, migration to TypeScript, and targeting
.d.tsfile generation from.jsfiles.Back to top
Committee representation
We are involved in several different committees, including TC39 and the Node modules group. We try to provide representation as
We're prioritizing forward compatibility with proposals/features that we've adopted early on, and we are also helping champion features which are highly-demanded from the community. As an example, our team is now involved in championing optional chaining and nullish coalescing. To maintain focus, we will likely only be engaged with a few proposals at a time.
We hold a policy of not implementing features unless they reach stage 3 and we have high confidence in them.
Developer productivity tools and integration
Editor productivity
.d.tsfiles@typespackageMore details here
While editor responsiveness would typically land under speed, scalability, and stability, it is worth noting here because it has consistently come up as a problem. We've fixed many responsiveness bugs, but we still have more feedback to investigate.
"Bread and butter" quick fixes and refactorings refer to a class of code modifications and fixes that are applicable to most users, and generally improve everyone's quality of life. These fixes are also useful for teaching users about language features and patterns. Expect more of these, and feel free to suggest some in separate issues!
We've heard that migration is still a common pain-point, and we would like to invest in ways to ease migration to TypeScript and typed JavaScript. We have ideas here like automatic refactorings for when a file is renamed from `.js` to `.ts`.
Managing declaration files continues to be a problem, and we have more ideas for good workflows since we last considered this. We'll have to rethink our approaches here.
When possible, we may provide more in-editor suggestions with quick fixes, though these are nice-to-haves compared to the other features mentioned here.
Back to top
Linting
ESLint is now a capable linter for TypeScript projects. There is room for improvement in editor scenarios, but we'll focus on core editor functionality and performance for JavaScript/TypeScript. We will monitor TypeScript integration in ESLint and assist the project when needed.
Back to top
Speed, scalability, and stability
More details here
Since the last roadmap, our benchmarking infrastructure is significantly better and uses more up-to-date versions of the 3rd party projects that we test against. We even have editor-style tests built into DefinitelyTyped to check whether any given test will significantly increase memory usage and keystroke delays. We're still continuing on automated testing infrastructure for TSServer to crawl external codebases to effectively fuzz-test them. ETW support is almost done, but is being wrapped up. We've also managed to address various regressions that have popped up.
In recent versions, we released the `--incremental` flag to enable faster compiles, with or without using project references. Still, when it comes to compiling and editing, our users have reported some scaling issues in performance. We're going to be reaching out to users to find the root cause of their issues, and finding patterns so that we can directly address the issues.
Back to top
Education and UX
New handbook
checkJsMore details here.
The handbook is close to done, and can be viewed here. We hope to be done with the core handbook in the coming months and to publish it to the new website around the end of the year.Back to top
Error and type display UX
More details here
We've made further improvements in UX and error messages, with help from the community, as well as [feedback from Microsoft's API teams](https://github.com//issues/30646) from user studies around Promise-based APIs using TypeScript. We'll continue to look for feedback from these sources.
We have been experimenting with editor UX changes that make it easy to explore types in quick info (editor tooltips) and error messages. We're holding these changes until we finish user studies on whether they actually help users fix issues more quickly.
Back to top
Playground and website
We've already replaced the playground, and have been investigating as to whether we can make nightly versions available. We will also be working on a redesign, new pages around community meetups/conferences, and integrating the new handbook into the site.
Community investment
DefinitelyTyped
Back to top
External contributors
Back to top
Partner teams
We continue to elicit feedback from various partner teams, including library authors and organizations/individuals using TypeScript in interesting or broadly applicable ways. This gives us insight on various things we could improve. If you or your organization have any interesting feedback, we'd probably love to hear from you!
Back to top
API Consumers
Back to top
Outreach
We want to encourage members of our team to be involved with the community, and write and talk about things that they find interesting. This keeps us close to our users and makes the project itself more approachable.
Internal engineering
Team infrastructure
The idea here is really anything that improves
for development on the TypeScript project and any of our satellite projects.
Back to top
Organizational guidance
Because we have the expertise, and because we are involved with the JavaScript community, we're able to provide a level of guidance across Microsoft to give users better experiences all around. Additionally, when we hear about major build regressions on large codebases, our internal teams can provide us with their source code, allowing us to create minimal repros (which is not always the case with external closed-source codebases). This work usually benefits external users in some way, whether it's because a bug fix generalizes, because we've produced better APIs, or because we've been able to extract new guidance.
Back to top
The text was updated successfully, but these errors were encountered: