Guild to Getting Started with Typescript and Best Practices
What is TypeScript?
Component and Features of TypeScript
- TypeScript has better typing. TypeScript has both static typing and a type interference system. The TLS system can infer typing based on the value of a variable if not declared.
The components of TypeScript are:
- The service. This system provides editor operations such as code formatting, colorization, and signature help.
How to install TypeScript
Now that you know why TypeScript is used, how is TypeScript installed?
TypeScript can be installed in three ways:
- An NPM Module. TypeScript is a package within the NPM registry known as “typescript.” It can be installed by typing “npm install typescript –save-dev.” From there, the compiler can be run by typing “npx tsc.”
- A NuGet Package. Through the “Manage NuGet Packages” window, TypeScript can be installed. Otherwise, it can be installed through the “NuGet Package Manager Console.”
- A Visual Studio Extension. If the project cannot use NuGet, the TypeScript Visual Studio Extension can instead be installed.
TypeScript Best Practices
#1 – Use “strict.” TypeScript doesn’t generally run with “strict” mode enabled. When you learn more about TypeScript, you can turn the “strict” mode off. However, as a beginner to the TypeScript parameters, it’s often easier to learn what does and doesn’t work by putting on “strict” mode.
#2 – Use opaque types
When creating code, it can be easy to use vague typing such as “strings,” which can essentially be anything. Opaque types give you more control over what is and isn’t considered to be acceptable within given parameters.
#3 – Get a code formatting system.
A code formatting system like “Prettier” can make code more attractive and manageable. This is especially true when developing large enterprise applications, as code may be written and maintained by different people with different styles.
#4 – Use Utility types.
Utility types can also be an excellent tool for ensuring that variables have the right types, even if those types might be fairly niched or (on the other side of the spectrum) too open.
#5- Don’t use custom TypeScript namespaces or modules.
Use import rather than “require.” Since ES6 modules are standard within TypeScript, “import” is used rather than “require.”