TypeScript 4.7 Iteration Plan

[DanielRosenwasser]

This document outlines our focused tasks for TypeScript 4.7. 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.

Date	Event
TBD	TypeScript 4.6 Release
April 1st	Create 4.7 Beta (4.7.0) Build for Testing
April 5th	TypeScript 4.7 Beta Release
May 6th	Create 4.7 RC (4.7.1) Build for Testing
May 10th	TypeScript 4.7 RC Release
May 20th	Create 4.7 Final (4.7.2) Build for Testing
May 24th	TypeScript 4.7 Final Release 🚀

Language and Compiler Features

• Node ESM UX Issues, and Move Node ESM Mode from Nightly
• Instantiation Expressions
• Import Strategies for import type and /// <reference />
• Investigate Contextually Typed And Compatible Operator
• lib.d.ts Updates

Editor Productivity

• Object Member Snippet Completions
• Investigate Go to JavaScript Implementation
• Prototype Virtual File System Support in TSServer
• Prototype Automatic Type Acquisition in Web Contexts
• Easy Run/Debug for Loose TypeScript Files
• Investigate TS Server Plugins on the Web

Performance

• Investigate Outstanding Performance Issues
• Find All References Refactoring and Optimizations
• Supporting Additional Trace Points
• Profiling/Tracing Mode Improvements
• Investigate Tooling for JIT Deoptimizations

Infrastructure

• Migrate to Modules
• Determine Shipping Strategy for Modules
• Fuzzer Improvements and Addressing Crashes
• Improving User Suite Reports
• Expand Perf Suite

Website

• Investigate Playground as a VS Code Extension

[vietanhtran16]

Hello, I am not sure if this is the right place for this but we got the below issue with version 4.7.0-dev.20220320 (this is automatically selected by VSCode) like the below image. We did some testing and noticed that this issue does not show up for version below 4.7.0, in our case 4.6.2 and 4.1.5 work fine. If this is not the right place for this, please let me know. Thanks

Context:

• We provide type safe fetch (its type is quite nested) which allows us to safely type the response based on the url of the request we are trying to make for a good dev experience
• We are getting the below error when we use our fetch in a Promise.all. My assumption is that Promise.all
  is trying to infer the type from our fetch type which is quite nested and caused this error on 4.7.0-dev.20220320

const [responseOne, responseTwo] = await Promise.all([ // it complains about the below error here
    fetch("https://something/v1", { req, timeout: 5000 }),
    fetch(
      "https://something/v2",
      { req, timeout: 5000 }
    )
  ])

[aladdin-add]

@vietanhtran16 yes, the issue is not for bug report, please file a new issue. :)

[vietanhtran16]

@vietanhtran16 yes, the issue is not for bug report, please file a new issue. :)

Cool I will file a new one

[DanielRosenwasser]

@typescript-bot create release-4.7

[typescript-bot]

Heya @DanielRosenwasser, I've started to create the release-4.7 branch for you. Here's the link to my best guess at the log.

[DanielRosenwasser]

Looks like it's probably failing because of the Node ESM stuff which we were hoping to unflag for the beta at the least. There's also some basic bug fixes I'd like us to pull in before beta, so maybe we'll go out on April 6th instead.

[DanielRosenwasser]

@typescript-bot create release-4.7

[typescript-bot]

Heya @DanielRosenwasser, I've started to create the release-4.7 branch for you. Here's the link to my best guess at the log.