GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — TypeScript 4.7 Iteration Plan · Issue #48027 · microsoft/TypeScript

TypeScript 4.7 Iteration Plan #48027

New issue
Copy link
New issue
Copy link
Closed
Closed
TypeScript 4.7 Iteration Plan#48027
Copy link
Labels
PlanningIteration plans and roadmappingIteration plans and roadmapping

Description

@DanielRosenwasser
Daniel Rosenwasser (DanielRosenwasser)
opened on Feb 24, 2022
Issue body actions

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
Reacted by Matt Bierner, electron-space, Tony Gentilcore, Liam Dyer, Matthias Hryniszak, Frédéric Espiau, Bart Lens, Johannes Schickling, ulrichb, Kirill Skvortsov and 9 more
Reacted by Alexander Kachkaev, Erik, Parbez, Okan YILDIRIM, Andy, Omri Luzon, six, C. T. Lin, Matt Bierner, Shrujal Shah and 12 more
Reacted by ikeryo1182, Joël Galeran, Denis Mukhametov, Sophie L, Simon Tretter, Kasper Peulen, Nico Jansen, Alan Song, Charles Samborski, Thijs Koerselman and 36 more

Activity

Next
  1. Daniel Rosenwasser (DanielRosenwasser)
    added
    PlanningIteration plans and roadmappingIteration plans and roadmapping
    on Feb 24, 2022
  2. Daniel Rosenwasser (DanielRosenwasser)
    pinned this issue on Feb 24, 2022
  3. vietanhtran16 commented on Mar 22, 2022

    @vietanhtran16
    vietanhtran16
    on Mar 22, 2022
    More actions

    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 }
        )
      ])
    

    image

  4. aladdin-add commented on Mar 22, 2022

    @aladdin-add
    唯然 (aladdin-add)
    on Mar 22, 2022
    More actions

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

  5. vietanhtran16 commented on Mar 22, 2022

    @vietanhtran16
    vietanhtran16
    on Mar 22, 2022
    More actions

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

    Cool I will file a new one

  6. DanielRosenwasser commented on Apr 3, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Apr 3, 2022
    MemberAuthor
    More actions

    TypeScript Bot (@typescript-bot) create release-4.7

  7. typescript-bot commented on Apr 3, 2022

    @typescript-bot
    TypeScript Bot (typescript-bot)
    on Apr 3, 2022
    Contributor
    More actions

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

  8. DanielRosenwasser commented on Apr 3, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Apr 3, 2022
    MemberAuthor
    More actions

    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.

    Reacted by Gonçalo Fernandes, Shrujal Shah, Danila Rodichkin, Daniel Derevjanik, Charles Samborski, Eugene and C. T. Lin
    Reacted by Toni Villena and Charles Samborski
  9. DanielRosenwasser commented on Apr 6, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Apr 6, 2022
    MemberAuthor
    More actions

    TypeScript Bot (@typescript-bot) create release-4.7

  10. typescript-bot commented on Apr 6, 2022

    @typescript-bot
    TypeScript Bot (typescript-bot)
    on Apr 6, 2022
    Contributor
    More actions

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

  11. DanielRosenwasser commented on Apr 6, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Apr 6, 2022
    MemberAuthor
    More actions

    The feature roadmap now better-reflects what we've been able to get done for 4.7.

    Reacted by Oleksandr Tarasiuk, Toni Villena, Victorien Elvinger, Raffael Campos, ExE Boss, electron-space, C. T. Lin and lin72h
    Reacted by Oleksandr Tarasiuk, Toni Villena, Alexander Kachkaev, Raffael Campos, Mathieu M-Gosselin, ExE Boss, C. T. Lin and lin72h
  12. Jack-Works commented on Apr 9, 2022

    @Jack-Works
    Jack Works (Jack-Works)
    on Apr 9, 2022
    Contributor
    More actions

    I still want to suggest typescript to drop Node 12 in new Node ESM. Lets start from Node 14. Node 14 has TLA support.

    image

    Node 12 will end LTS this month.

    Reacted by Victorien Elvinger, Toni Villena, C. T. Lin, Jacob Ley, João Ferreira, Hugo, Michael Hays, 湫曗, thermarthae, Nikolai A. G. and 24 more
  13. lvelden commented on Apr 13, 2022

    @lvelden
    Lisa Velden (lvelden)
    on Apr 13, 2022
    More actions

    Hi! I've seen the 4.7-beta announcement, but it's not listed under releases and there's also no v4.7-beta tag. Are you planning on adding this?

    Reacted by Bernard
  14. DanielRosenwasser commented on Apr 13, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Apr 13, 2022
    MemberAuthor
    More actions

    Sorry, tag for 4.7 beta should be out https://github.com/microsoft/TypeScript/releases/tag/v4.7-beta

    Reacted by Alexander Kachkaev
  15. diervo commented on Apr 15, 2022

    @diervo
    Diego Ferreiro Val (diervo)
    on Apr 15, 2022
    More actions

    Daniel Rosenwasser (@DanielRosenwasser) is there a specific tag or semantics for filing issues against this beta that will help streamline the process?

  16. 1 remaining item

  17. DanielRosenwasser commented on May 6, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 6, 2022
    MemberAuthor
    More actions

    We've moved resolution-mode from import type and export type into nightly-only, so I cannot summon the bot. The bump to RC is at #49007.

  18. DanielRosenwasser commented on May 11, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 11, 2022
    MemberAuthor
    More actions

    4.8 Iteration Plan is available at #49074

  19. RyanCavanaugh commented on May 19, 2022

    @RyanCavanaugh
    Ryan Cavanaugh (RyanCavanaugh)
    on May 19, 2022
    Member
    More actions

    TypeScript Bot (@typescript-bot) bump release-4.7

  20. typescript-bot commented on May 19, 2022

    @typescript-bot
    TypeScript Bot (typescript-bot)
    on May 19, 2022
    Contributor
    More actions

    Heya Ryan Cavanaugh (@RyanCavanaugh), I've started to update the version number on release-4.7 to 4.7.2 for you. Here's the link to my best guess at the log.

  21. Jamesernator commented on May 24, 2022

    @Jamesernator
    James Browning (Jamesernator)
    on May 24, 2022
    More actions

    Just wanted to point out one mistake in the TypeScript 4.7 RC release notes that should probably be fixed for the full release and that's that the line:

    Certain global-like values like require() and process cannot be used directly.
    

    Is actually incorrect for process, unlike require which a per-cjs-module injected thing, the process object is actually just a property of global so is usable in ESM as a global without problems.

    An alternative object for the sentence could the module per-cjs-module object i.e.:

    Certain global-like values like require() and module cannot be used directly.
    
    Reacted by Alexander Kachkaev and Eugene
  22. DanielRosenwasser commented on May 24, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 24, 2022
    MemberAuthor
    More actions

    Thank you for that correction!

  23. DanielRosenwasser commented on May 24, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on May 24, 2022
    MemberAuthor
    More actions

    TypeScript 4.7 is now out!

    Reacted by Jan Kühle, Erik Krogh Kristensen, Branch Vincent, Alexander Kachkaev, Dominik, why520crazy, C. T. Lin, Oleksandr Tarasiuk, Shrujal Shah, Rob Palmer and 3 more
    Reacted by Alexander Kachkaev, why520crazy, C. T. Lin, Oleksandr Tarasiuk, Fathy Boundjadj and Peter Matta
    Reacted by Toni Villena, why520crazy, Oleksandr Tarasiuk and Peter Matta
  24. HolgerJeromin commented on May 25, 2022

    @HolgerJeromin
    Holger Jeromin (HolgerJeromin)
    on May 25, 2022
    Contributor
    More actions

    Happy to test, but linked Typescript SDK has a 404 and nuget.org has a 4.7.2-rc (hu?).
    But npm is available :-)

    ref #48456

  25. DensedyGot commented on May 26, 2022

    @DensedyGot
    Densedy Isaguirre (DensedyGot)
    on May 26, 2022
    More actions

    I installed the typescript 4.7.2 but I encountered an error

    Module build failed (from ./node_modules/ts-loader/index.js):
    Error: Debug Failure. False expression: Non-string value passed to ts.resolveTypeReferenceDirective, likely by a wrapping package working with an outdated resolveTypeReferenceDirectives signature. This is probably not a problem in TS itself.

    I'm using [email protected] and [email protected]

    Here are some of the packages I used
    @fluentui/[email protected]
    @types/[email protected]
    [email protected]
    [email protected]
    @types/[email protected]
    @typescript-eslint/[email protected]
    @typescript-eslint/[email protected]
    [email protected]
    [email protected]
    [email protected]
    [email protected]
    [email protected]
    [email protected]

    Reacted by Stiliyan Lazarov, Peter Matta, Robert Kranz and Agis Anastasopoulos
  26. DanielRosenwasser commented on Jun 3, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Jun 3, 2022
    MemberAuthor
    More actions

    TypeScript Bot (@typescript-bot) bump release-4.7

  27. typescript-bot commented on Jun 3, 2022

    @typescript-bot
    TypeScript Bot (typescript-bot)
    on Jun 3, 2022
    Contributor
    More actions

    Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to update the version number on release-4.7 to 4.7.3 for you. Here's the link to my best guess at the log.

  28. DanielRosenwasser commented on Jun 16, 2022

    @DanielRosenwasser
    Daniel Rosenwasser (DanielRosenwasser)
    on Jun 16, 2022
    MemberAuthor
    More actions

    TypeScript Bot (@typescript-bot) bump release-4.7

  29. typescript-bot commented on Jun 16, 2022

    @typescript-bot
    TypeScript Bot (typescript-bot)
    on Jun 16, 2022
    Contributor
    More actions

    Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to update the version number on release-4.7 to 4.7.4 for you. Here's the link to my best guess at the log.

  30. Ryan Cavanaugh (RyanCavanaugh)
    closed this as completedon Jun 24, 2022
  31. Ryan Cavanaugh (RyanCavanaugh)
    unpinned this issue on Jun 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    PlanningIteration plans and roadmappingIteration plans and roadmapping

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.