upgrade typescript dependencies

[alexandratran]

Description

Upgrade typescript and tsconfig dependencies for Docusaurus v3: https://docusaurus.io/docs/migration/v3#typescript-v51 Also, my npm install and yarn install stalls and times out when I use Node version <20, preventing a local build, so this PR updates the .nvmrc file to v20.

Issue(s) fixed

Fixes #

Preview

Checklist

Complete this checklist before merging your PR:

• [ ] If this PR contains a major change to the documentation content, I have added an entry to the top of the "What's new?" page.
• [ ] The proposed changes have been reviewed and approved by a member of the documentation team.

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@docusaurus/core@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+997	87.1 MB
npm/@docusaurus/eslint-plugin@3.4.0	Transitive: environment, filesystem	+42	3.68 MB
npm/@docusaurus/module-type-aliases@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+210	21.9 MB
npm/@docusaurus/plugin-client-redirects@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+364	48 MB
npm/@docusaurus/plugin-content-docs@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+547	56.3 MB
npm/@docusaurus/theme-common@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+558	57.8 MB
npm/@docusaurus/theme-mermaid@3.4.0	Transitive: environment, eval, filesystem, network, shell, unsafe	+576	103 MB
npm/@docusaurus/tsconfig@3.0.0	None	0	2.13 kB	slorber
npm/@lavamoat/allow-scripts@3.0.4	environment Transitive: filesystem, network, shell, unsafe	+126	8.38 MB	boneskull
npm/@metamask/design-tokens@1.12.0	None	0	113 kB	gudahtt
npm/@metamask/docusaurus-openrpc@0.4.1	Transitive: environment, eval, filesystem, network, shell, unsafe	+864	118 MB	metamaskbot
npm/eslint-plugin-react@7.34.2	filesystem Transitive: environment, eval	+105	6.02 MB	ljharb
npm/typescript@5.2.2	None	0	40.6 MB	typescript-bot

🚮 Removed packages: npm/@docusaurus/core@3.3.2, npm/@docusaurus/eslint-plugin@3.3.2, npm/@docusaurus/module-type-aliases@3.3.2, npm/@docusaurus/plugin-client-redirects@3.3.2, npm/@docusaurus/plugin-content-docs@3.3.2, npm/@docusaurus/theme-common@3.3.2, npm/@docusaurus/theme-mermaid@3.3.2, npm/@lavamoat/allow-scripts@2.5.1, npm/@metamask/design-tokens@1.13.0, npm/@metamask/docusaurus-openrpc@0.4.0, npm/@tsconfig/docusaurus@1.0.7, npm/eslint-plugin-react@7.34.1, npm/typescript@4.9.5

View full report↗︎

[socket-security[bot]]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Shell access	npm/foreground-child@3.1.1	Module: child_process Location: Package overview	package-lock.json package.json
Shell access	npm/foreground-child@3.1.1	Module: child_process Location: Package overview	package-lock.json package.json
New author	npm/abbrev@2.0.0	New Author: lukekarrys Previous Author: isaacs	package-lock.json package.json
Network access	npm/socks-proxy-agent@8.0.3	Module: net Location: Package overview	package-lock.json package.json
Network access	npm/agent-base@7.1.1	Module: http Location: Package overview	package-lock.json package.json
Network access	npm/agent-base@7.1.1	Module: https Location: Package overview	package-lock.json package.json
Network access	npm/agent-base@7.1.1	Module: net Location: Package overview	package-lock.json package.json
Network access	npm/@npmcli/agent@2.2.2	Module: net Location: Package overview	package-lock.json package.json
Network access	npm/@npmcli/agent@2.2.2	Module: tls Location: Package overview	package-lock.json package.json
Network access	npm/@npmcli/agent@2.2.2	Module: dns Location: Package overview	package-lock.json package.json
Network access	npm/@npmcli/agent@2.2.2	Module: http-proxy-agent Location: Package overview	package-lock.json package.json
Network access	npm/@npmcli/agent@2.2.2	Module: https-proxy-agent Location: Package overview	package-lock.json package.json
New author	npm/validate-npm-package-name@5.0.1	New Author: npm-cli-ops Previous Author: lukekarrys	package-lock.json package.json
New author	npm/@metamask/open-rpc-docs-react@0.2.0	New Author: mcmire Previous Author: metamaskbot	package-lock.json package.json
Shell access	npm/update-browserslist-db@1.0.16	Module: child_process Location: Package overview	package-lock.json package.json
New author	npm/micromatch@4.0.7	New Author: paulmillr Previous Author: jonschlinkert	package-lock.json package.json
Unstable ownership	npm/micromatch@4.0.7	Author: paulmillr	package-lock.json package.json

View full report↗︎

Next steps

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/foreground-child@3.1.1
• @SocketSecurity ignore npm/abbrev@2.0.0
• @SocketSecurity ignore npm/socks-proxy-agent@8.0.3
• @SocketSecurity ignore npm/agent-base@7.1.1
• @SocketSecurity ignore npm/@npmcli/agent@2.2.2
• @SocketSecurity ignore npm/validate-npm-package-name@5.0.1
• @SocketSecurity ignore npm/@metamask/open-rpc-docs-react@0.2.0
• @SocketSecurity ignore npm/update-browserslist-db@1.0.16
• @SocketSecurity ignore npm/micromatch@4.0.7