Sync with TypeScript-Website @ fa87fd0f

[SyncDocsBot]

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

• tree.
• tree.
• 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	Feb 21, 2025 1:24am

[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 Choosing Compiler Options.md

Line	Typo
12	onment, both in terms of what globals are available and in terms of
12	use this guide once for each tsconfig.json. For library-like projects wit
16	ndler projects for now. [Some bundlers](https://andrewbranch.github.
16	h TypeScript cannot currently analyze with `"moduleResolution": "bu
69	### I’m using ts-node
71	ts-node attempts to be compatible wit
71	e-outputs-in-node). Refer to [ts-node documentation](https://typest
75	Whereas ts-node makes minimal modifications t
104	type declaration files, while erroring on imports that would normall
104	hat would normally resolve in node_modules:
112	lying on nodenext’s default node_modules lookups, or on paths, to di
154	em, it almost always works in bundlers as well. If you’re using a th
173	orks both in Node.js and in bundlers.
175	owing code that only works in bundlers to be produced. Likewise, `"m
175	work in other runtimes and in bundlers.
176	also ensures you don’t access globals that may not be available in
189	es. Both of these represent a tradeoff between developer experience
196	n a bundler but are unsafe in Node.js. On the other hand, using `"mo
209	it-related options set in the tsconfig.json. While third-party emitters ar

Generated by 🚫 dangerJS against fa87fd0