Fix nav

Author: orta

pages/release notes/TypeScript 3.8.md

@@ -1,12 +1,12 @@
-* [Type-Only Imports and Exports](#type-only-imports-exports)
+* [Type-Only Imports and Exports](#type-only-imports-and-exports)
 * [ECMAScript Private Fields](#ecmascript-private-fields)
 * [`export * as ns` Syntax](#export-star-as-namespace-syntax)
 * [Top-Level `await`](#top-level-await)
 * [JSDoc Property Modifiers](#jsdoc-modifiers)
 * [Better Directory Watching on Linux and `watchOptions`](#better-directory-watching)
 * ["Fast and Loose" Incremental Checking](#assume-direct-dependencies)
 
-## <span id="type-only-imports-exports" /> Type-Only Imports and Export
+## Type-Only Imports and Exports
 
 This feature is something most users may never have to think about; however, if you've hit issues under `--isolatedModules`, TypeScript's `transpileModule` API, or Babel, this feature might be relevant.
 
@@ -61,7 +61,7 @@ This flag takes 3 different values:
 
 For more information about the feature, you can [take a look at the pull request](https://github.com/microsoft/TypeScript/pull/35200), and [relevant changes](https://github.com/microsoft/TypeScript/pull/36092/) around broadening where imports from an `import type` declaration can be used.
 
-## <span id="ecmascript-private-fields" /> ECMAScript Private Fields
+## ECMAScript Private Fields
 
 TypeScript 3.8 brings support for ECMAScript's private fields, part of the [stage-3 class fields proposal](https://github.com/tc39/proposal-class-fields/).
 
@@ -262,7 +262,7 @@ A final consideration might be speed: `private` properties are no different from
 In contrast, because `#` private fields are downleveled using `WeakMap`s, they may be slower to use.
 While some runtimes might optimize their actual implementations of `#` private fields, and even have speedy `WeakMap` implementations, that might not be the case in all runtimes.
 
-## <span id="export-star-as-namespace-syntax" /> `export * as ns` Syntax
+## `export * as ns` Syntax
 
 It's often common to have a single entry-point that exposes all the members of another module as a single member.
 
@@ -280,7 +280,7 @@ export * as utilities from "./utilities.js";
 This is a nice quality-of-life improvement to JavaScript, and TypeScript 3.8 implements this syntax.
 When your module target is earlier than `es2020`, TypeScript will output something along the lines of the first code snippet.
 
-## <span id="top-level-await" /> Top-Level `await`
+## Top-Level `await`
 
 TypeScript 3.8 provides support for a handy upcoming ECMAScript feature called "top-level `await`".
 
@@ -318,13 +318,13 @@ Support within several environments and bundlers may be limited or may require e
 
 For more information on our implementation, you can [check out the original pull request](https://github.com/microsoft/TypeScript/pull/35813).
 
-## <span id="es2020-for-target-and-module" /> `es2020` for `target` and `module`
+## `es2020` for `target` and `module`
 
 TypeScript 3.8 supports `es2020` as an option for `module` and `target`.
 This will preserve newer ECMAScript 2020 features like optional chaining, nullish coalescing, `export * as ns`, and dynamic `import(...)` syntax.
 It also means `bigint` literals now have a stable `target` below `esnext`.
 
-## <span id="jsdoc-modifiers" /> JSDoc Property Modifiers
+## JSDoc Property Modifiers
 
 TypeScript 3.8 supports JavaScript files by turning on the `allowJs` flag, and also supports *type-checking* those JavaScript files via the `checkJs` option or by adding a `// @ts-check` comment to the top of your `.js` files.
 
@@ -380,7 +380,7 @@ new Foo().stuff++;
 // Cannot assign to 'stuff' because it is a read-only property.
 ```
 
-## <span id="better-directory-watching" /> Better Directory Watching on Linux and `watchOptions`
+## Better Directory Watching on Linux and `watchOptions`
 
 TypeScript 3.8 ships a new strategy for watching directories, which is crucial for efficiently picking up changes to `node_modules`.
 

pages/release notes/TypeScript 3.9.md

@@ -1,15 +1,15 @@
-* [Improvements in Inference and `Promise.all`](#promise-improvements)
+* [Improvements in Inference and `Promise.all`](#improvements-in-inference-and-promiseall)
 * [Speed Improvements](#speed-improvements)
-* [`// @ts-expect-error` Comments](#ts-expect-error-comments)
-* [Uncalled Function Checks in Conditional Expressions](#uncalled-in-conditionals)
+* [`// @ts-expect-error` Comments](#-ts-expect-error-comments)
+* [Uncalled Function Checks in Conditional Expressions](#uncalled-function-checks-in-conditional-expressions)
 * [Editor Improvements](#editor-improvements)
-    * [CommonJS Auto-Imports in JavaScript](#cjs-auto-imports)
-    * [Code Actions Preserve Newlines](#preserve-newlines)
-    * [Quick Fixes for Missing Return Expressions](#missing-returns)
-    * [Support for "Solution Style" `tsconfig.json` Files](#solution-style-tsconfig)
+    * [CommonJS Auto-Imports in JavaScript](#commonjs-auto-imports-in-javascript)
+    * [Code Actions Preserve Newlines](#code-actions-preserve-newlines)
+    * [Quick Fixes for Missing Return Expressions](#quick-fixes-for-missing-return-expressions)
+    * [Support for "Solution Style" `tsconfig.json` Files](#support-for-solution-style-tsconfigjson-files)
 * [Breaking Changes](#breaking-changes)
 
-## <span id=promise-improvements /> Improvements in Inference and `Promise.all`
+## Improvements in Inference and `Promise.all`
 
 Recent versions of TypeScript (around 3.7) have had updates to the declarations of functions like `Promise.all` and `Promise.race`.
 Unfortunately, that introduced a few regressions, especially when mixing in values with `null` or `undefined`.
@@ -47,7 +47,7 @@ We initially anticipated shipping `awaited` in TypeScript 3.9, but as we've run
 As a result, we've decided to pull the feature out of our main branch until we feel more confident.
 We'll be experimenting more with the feature, but we won't be shipping it as part of this release.
 
-## <span id=speed-improvements /> Speed Improvements
+## Speed Improvements
 
 TypeScript 3.9 ships with many new speed improvements.
 Our team has been focusing on performance after observing extremely poor editing/compilation speed with packages like material-ui and styled-components.
@@ -69,7 +69,7 @@ TypeScript 3.9 addresses this issue by [changing the internals of how the compil
 
 While there's still room for improvement, we hope this work translates to a snappier experience for everyone!
 
-## <span id=ts-expect-error-comments /> `// @ts-expect-error` Comments
+## `// @ts-expect-error` Comments
 
 Imagine that we're writing a library in TypeScript and we're exporting some function called `doStuff` as part of our public API.
 The function's types declare that it takes two `string`s so that other TypeScript users can get type-checking errors, but it also does a runtime check (maybe only in development builds) to give JavaScript users a helpful error.
@@ -127,7 +127,7 @@ Unused '@ts-expect-error' directive.
 We'd like to extend a big thanks to [Josh Goldberg](https://github.com/JoshuaKGoldberg), the contributor who implemented this feature.
 For more information, you can take a look at [the `ts-expect-error` pull request](https://github.com/microsoft/TypeScript/pull/36014).
 
-### <span id=what-about-ts-ignore /> `ts-ignore` or `ts-expect-error`?
+### `ts-ignore` or `ts-expect-error`?
 
 In some ways `// @ts-expect-error` can act as a suppression comment, similar to `// @ts-ignore`.
 The difference is that `// @ts-ignore` will do nothing if the following line is error-free.
@@ -147,7 +147,7 @@ Pick `ts-ignore` if:
 * you are in the middle of an upgrade between two different versions of TypeScript, and a line of code errors in one version but not another.
 * you honestly don't have the time to decide which of these options is better.
 
-## <span id=uncalled-in-conditionals /> Uncalled Function Checks in Conditional Expressions
+## Uncalled Function Checks in Conditional Expressions
 
 In TypeScript 3.7 we introduced *uncalled function checks* to report an error when you've forgotten to call a function.
 
@@ -191,7 +191,7 @@ function getAllFiles(startFileName: string) {
 
 https://github.com/microsoft/TypeScript/issues/36048
 
-## <span id=editor-improvements /> Editor Improvements
+## Editor Improvements
 
 The TypeScript compiler not only powers the TypeScript editing experience in most major editors, it also powers the JavaScript experience in the Visual Studio family of editors and more.
 Using new TypeScript/JavaScript functionality in your editor will differ depending on your editor, but
@@ -200,7 +200,7 @@ Using new TypeScript/JavaScript functionality in your editor will differ dependi
 * Visual Studio 2017/2019 have [the SDK installers above] and [MSBuild installs](https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild).
 * Sublime Text 3 supports [selecting different versions of TypeScript](https://github.com/microsoft/TypeScript-Sublime-Plugin#note-using-different-versions-of-typescript)
 
-### <span id=cjs-auto-imports /> CommonJS Auto-Imports in JavaScript
+### CommonJS Auto-Imports in JavaScript
 
 One great new improvement is in auto-imports in JavaScript files using CommonJS modules.
 
@@ -223,7 +223,7 @@ TypeScript now automatically detects the types of imports you're using to keep y
 
 For more details on the change, see [the corresponding pull request](https://github.com/microsoft/TypeScript/pull/37027).
 
-### <span id=preserve-newlines /> Code Actions Preserve Newlines
+### Code Actions Preserve Newlines
 
 TypeScript's refactorings and quick fixes often didn't do a great job of preserving newlines.
 As a really basic example, take the following code.
@@ -284,7 +284,7 @@ function printSquares() {
 
 You can see more about the implementation [in this pull request](https://github.com/microsoft/TypeScript/pull/36688)
 
-### <span id=missing-returns /> Quick Fixes for Missing Return Expressions
+### Quick Fixes for Missing Return Expressions
 
 There are occasions where we might forget to return the value of the last statement in a function, especially when adding curly braces to arrow functions.
 
@@ -300,7 +300,7 @@ Thanks to [a pull request](https://github.com/microsoft/TypeScript/pull/26434) f
 
 ![TypeScript fixing an error where no expression is returned by adding a `return` statement or removing curly braces.](https://devblogs.microsoft.com/typescript/wp-content/uploads/sites/11/2020/04/missingReturnValue-3-9.gif)
 
-### <span id=solution-style-tsconfig /> Support for "Solution Style" `tsconfig.json` Files
+### Support for "Solution Style" `tsconfig.json` Files
 
 Editors need to figure out which configuration file a file belongs to so that it can apply the appropriate options and figure out which other files are included in the current "project".
 By default, editors powered by TypeScript's language server do this by walking up each parent directory to find a `tsconfig.json`.
@@ -325,7 +325,7 @@ Here, none of these `tsconfig.*.json` files get picked up by the server, but we'
 TypeScript 3.9 adds support to editing scenarios for this configuration.
 For more details, take a look at [the pull request that added this functionality](https://github.com/microsoft/TypeScript/pull/37239).
 
-## <span id=breaking-changes /> Breaking Changes
+## Breaking Changes
 
 ### Parsing Differences in Optional Chaining and Non-Null Assertions