add Chinese(zh) translate version of Handbook.md

[xgqfrms]

No description provided.

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @Kingwl - if they write a comment saying "LGTM" then it will be merged.

[github-actions]

Translation of The Handbook.md

---

title: TypeScript manual
layout: docs
permalink: /zh/docs/handbook/intro.html
oneline: The first step in learning TypeScript

handbook: "true"

About this manual

More than 20 years after being introduced to the programming community, JavaScript is now one of the most widely used cross-platform languages of all time. What started as a small scripting language for adding trivial interactivity to web pages has grown to become the language of choice for front-end and back-end applications of all sizes. While programs written in JavaScript have grown exponentially in size, scope, and complexity, the JavaScript language has no ability to express relationships between different units of code. Combined with JavaScript's rather specific runtime semantics, this mismatch between language and program complexity makes JavaScript development a difficult task to manage at scale.

The most common type of error written by a programmer can be described as a type error: a value of a certain type is used where a value of a different type is expected. This can be due to simple spelling mistakes, a failure to understand the library's API surface, incorrect assumptions about runtime behavior, or other errors. The goal of TypeScript is to be a static type checker for JavaScript programs - in other words, a tool that runs before the code runs (static) and ensures that the program is of the correct type (type checking).

If you are using TypeScript without a background in JavaScript and intend to use TypeScript as your first language, we recommend that you start reading first Microsoft Learn JavaScript tutorials on the document or read JavaScript in Mozilla web documentation。
If you have experience with other languages, you should be able to grasp JavaScript syntax very quickly by reading the manual.

What is the structure of this manual

The manual is divided into two parts:

• handbook

  The TypeScript manual is intended to be a comprehensive document that explains TypeScript to everyday programmers. You can read the manual from top to bottom in the left navigation.

  You should expect that each chapter or page will give you a deep understanding of a given concept. The TypeScript manual is not a complete language specification, but it is intended to be a comprehensive guide to all features and behaviors of the language.

  Readers who complete the walkthrough should be able to:

  • Read and understand common TypeScript syntax and patterns
  • Explains the impact of important compiler options
  • Type system behavior is predicted correctly in most cases

  For clarity and brevity, the main content of this manual does not explore all edge cases or details of the features covered. You can find more details about specific concepts in the reference article.

• Reference files

  The reference sections below the manual in the navigation are intended to provide a richer understanding of how specific parts of TypeScript work. You can read it from top to bottom, but each section is designed to provide a deeper explanation of a single concept – meaning there is no goal of continuity.

Non-target

The manual is also intended to be a concise document that can be easily read in a few hours. For the sake of brevity, some topics will not be covered.

Specifically, the manual does not fully cover core JavaScript fundamentals such as functions, classes, and closures. Where appropriate, we will include links to background readings that you can use to read about these concepts.

The manual is also not intended to replace the language specification. In some cases, edge cases or formal descriptions of behavior are skipped in favor of higher-level explanations that are easier to understand. Instead, there are separate reference pages that more accurately and formally describe many aspects of TypeScript behavior. The reference page is not intended for readers who are new to TypeScript, so they may use advanced terms or reference topics that you haven't read yet.

Finally, the manual does not cover how TypeScript interacts with other tools unless necessary. Topics such as how to configure TypeScript using webpack, rollup, parcel, react, babel, closure, lerna, rush, bazel, preact, vue, angular, svelte, jquery, yarn, or npm are out of scope - you can find these resources elsewhere online.

Get started now

Get startedThe basicsBefore that, we recommend that you read one of the following introductory pages. These introductions are intended to highlight the main similarities and differences between TypeScript and your favorite programming languages and to clarify common misconceptions about these languages.

• TypeScript for novice programmers
• TypeScript for JavaScript programmers
• TypeScript for OOP programmers
• TypeScript for functional programmers

Otherwise, jump to The basics Or get a copy Epub or .PDF A copy of the format.

Generated by 🚫 dangerJS against da3a441

[xgqfrms]

LGTM