Sync with TypeScript-Website @ 711dee4f

[SyncDocsBot]

合并自 https://github.com/microsoft/TypeScript-Website.git @ 711dee4
下面的文件存在冲突，请处理后合并：

• tree.
• tree.
• tree.

不要 Squash 此 Pull Request！！！

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
ts-zh-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 7, 2025 1:41am

[github-actions]

Got false positives?

Make changes to the global settings spellcheck.json in /microsoft/TypeScript-Website.

Make changes to this repo's settings in spellcheck.json.

Typos for Reference.md

Line	Typo
14	ed in TypeScript files and/or JSDoc comments.
18	Type aliases, interfaces, enums, and namespaces can be export
105	This is especially useful in JSDoc comments in JavaScript files,
116	Script files can use a direct analog of module.exports = ... and
208	re intended to run in Node.js v12 or later, whether they use ES
210	the latest stable versions of Node.js. The following table summarize
212	JSON imports
214
215
224	pe": "module"` to the project package.json.
233	flect the behavior of Node.js v22.12.0 and later, require can refe
281	re intended to run in Node.js v12 or later, whether they use ES
289	preserved in the output, and CommonJS-style import x = require("...") a
291	e capabilities of most modern bundlers, as well as the Bun runtime.
328	moduleResolution bundler` for bundlers, Bun, and tsx.
329	- Do not use for Node.js. Use node16, node18, or `n
329	e.json to emit ES modules for Node.js.
364	to emit CommonJS modules for Node.js.
425	- Designed for use with the [SystemJS module loader](https://github
467	Designed for AMD loaders like RequireJS.
554	n file with the same name and analagous file extension.
600	even though some runtimes and bundlers do.
624	browser before ESM existed or bundlers were widely used), it still h
642	so common for apps built with bundlers to define convenience path al
679	# paths should not point to monorepo packages or node_modules pack
679	point to monorepo packages or node_modules packages
696	s referencing each other in a monorepo. Instead of using paths to
696	com/en/docs/workspaces/), or [pnpm](https://pnpm.io/workspaces)
696	s especially important if the monorepo packages will be published to
734	##### Fallbacks
760	node_modules` subdirectories. Bundlers conveniently adopted this beh
760	ependencies, as they would in Node.js. All of TypeScript’s `moduleRe
781	e of "exports" prevents any subpaths not explicitly listed or matc
783	##### Example: subpaths, conditions, and extension su
879	##### Example: subpath patterns
907	mple: "exports" block other subpaths
923	package root? No, it has a subpath dist/index.js.
926	orts"` prevents resolving any subpaths that cannot be matched throug
930	s` packages, according to the subpath being resolved. This allows p
930	ersions (through a tool like [downlevel-dts](https://github.com/sandersn/
954	4. Are we resolving a subpath after the package name? **No,
981	4. Are we resolving a subpath after the package name? **No,
989	ule specifier does not have a subpath after the package name or pac
1001	agejson-typesversions) apply, subpaths of a bare package specifier r
1014	the "exports" field of that package.json. Both of these features allow
1067	node_modules` dependency with subpath pattern
1102	esolution behavior of Node.js v12 and later. (node16 and `nod
1106	d compatibility with existing CommonJS-format type declarations):
1145	ior common to most JavaScript bundlers. In short, this means support
1145	this means supporting all the behaviors traditionally associated with
1158	n combination with --noEmit—bundlers typically process raw .ts f
1187	Node.js versions earlier than v12. It should no longer be used.

Generated by 🚫 dangerJS against 711dee4