Update typescript: 3.9.6 → 3.9.10 (patch)

[depfu[bot]]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ typescript (3.9.6 → 3.9.10) · Repo

Release Notes

3.9.10

This release ships both an overall performance improvement, along with a mitigation for a performance regression when upgrading to Node.js 16. See the change for more details.

3.9.9

This release contains a fix for an issue when language service plugins have no specified name.

3.9.7

For release notes, check out the release announcement.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v3.9.0 (Beta).
• fixed issues query for Typescript v3.9.1 (RC).
• fixed issues query for Typescript v3.9.2 (Final).
• fixed issues query for Typescript v3.9.3 (patch release).
• fixed issues query for Typescript v3.9.5 (patch release).
• fixed issues query for Typescript v3.9.6 (patch release).
• fixed issues query for Typescript v3.9.7 (patch release).

(note, 3.9.4 was intentionally skipped due to minor complications in publishing)

Downloads are available on:

• npm
• Visual Studio 2017/2019 (Select new version in project options)
• NuGet package

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 13 commits:

• Bump version to 3.9.10 and LKG
• Backport package-lock infra changes to 3.9 (#44608)
• Pass throwIfNoEntry to fs.statSync (#41604) (#44582)
• Bump version to 3.9.9 and LKG
• Handle if plugin doesnt specify name (#42722)
• Bump version to 3.9.8 and LKG
• Allow only package names as plugin names
• Merge pull request #39988 from amcasey/pinned-release-3.9
• Drop testing of node 8
• Make release-3.9 buildable
• Bump version to 3.9.7 and LKG
• Cherry-pick PR #39599 into release-3.9 (#39601)
• Cherry-pick PR #39573 into release-3.9 (#39602)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)