Microsoft has detailed the <a href="https://github.com/Microsoft/TypeScript/issues/29288" target="_blank">priorities that will drive TypeScript development during the first six months of 2019</a>. Albeit not yet committed, the current roadmap includes enhanced core type system, maximizing forward compatibility with <a href="https://github.com/tc39" target="_blank">new ECMA features</a>, improving tools, including editor support and linting, and more.
Microsoft has detailed the priorities that will drive TypeScript development during the first six months of 2019. Albeit not yet committed, the current roadmap includes enhanced core type system, maximizing forward compatibility with new ECMA features, improving tools, including editor support and linting, and more.
Another front where Microsoft will be active is representation within standardization committees, particularly the TC39 committee, which is going to bring the next ECMA standard, and the Node modules group. Highest priority will be influencing the committee's work to ensure better compatibility with proposed features that TypeScript adopted earlier on, such as class fields, decorators, module interoperability, null propagation/coalescing, etc.
Improving tools and developers productivity is also among Microsoft´s goals for the evolution of the TypeScript ecosystem. This includes editor features such as “proactive” quick fixes that will suggest possible changes to improve the code, for example detecting implicit any use even when not using the noImplicitAnycompiler setting and inferring an appropriate type. Improving how developers deal with declaration files is also center stage, with the aim of finding a workflow to help developer handle the case where a type file is not available in DefinitelyTyped or fix erroneous declaration files. Additionally, Microsoft also plans to improve the TypeScript linter (TSLint) performance and the TypeScript server (TSServer) speed, scalability, and stability. Interestingly, to solve TSLint performance issues, Microsoft will leverage ESLint, which they say has the kind of architecture they are striving for, and send contributions to bring its TypeScript support to parity with TSLint.
As a final note, Microsoft is also planning to write a new TypeScript handbook, improve compiler diagnostics, update the TypeScript playground, and extend the DefinitelyTYped infrastructure.
You can get the full details in the official GitHub Roadmap page.
This article is not just about Builder Pattern in JS/TS, I will be explaining my thought process behind it and see if you can relate yourself to this. I believe everybody has a unique way of solving problems, hope you get something to learn from it.