Suggestion Backlog Slog, 10/11/2021

[andrewbranch]

(Notes by @DanielRosenwasser)

• allow voluntary .ts suffix for import paths #37582

  • Basically Deno requires this.

  • What are the other implications here? Does node12 + this mode allow you to use Deno.

  • Bit of a trap if we do this not-carefully.

  • Could imagine with noEmit (otherwise, have to emit .ts files).

  • Curious to see how the various bundlers react when you say .js when you're really going to hit .ts.

  • Multiple use-cases for wanting to write .ts - but don't like the idea of adding one piece of the full story which doesn't really address the true scenario.

  • Also, at least half of users are asking for importing .ts files and having us rewrite the extension.

  • Next steps: try to understand how significant the demand is for Deno support in tsc and what it would require from us to do

• Optional chaining of unknown should be unknown #37700

  • Shouldn't you also be able to do this on object and {}?

  • How far do you go? unknown + unknown is unknown too.

  • a?.toStirng would be valid - no way to catch this because it's "technically correct". Allows inconsistent accesses.

    if (a?.foo) {
        a?.boo.yadda(); // oops
    }

  • Not in the business of creating new anys.

  • Action: close issue