typings vs @types NPM scope

typescript npm typescript-typings
Estus Flask picture Estus Flask · Sep 1, 2016 · Viewed 13.9k times · Source

In some cases typings is used for handling TypeScript definitions (e.g. angular/angular2-seed).

In other cases scoped NPM @types packages are used with no typings involved (e.g. AngularClass/angular2-webpack-starter).

What are the practical differences between them? Does one of them offer benefits for TypeScript development that the other doesn't?

Answer

ordepim picture ordepim · Sep 1, 2016

@types is the new way to install the definitions in typescript 2.0. It unifies the management of definitions and packages. So that you do not need multiple tools and config files. Only going to need npm and package.json instead of having to have npm, package.json, typings, typings.json. It basically makes installing and managing definitions easier but it is the same as typings.

You can read more about it here: https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/

Related questions

How do I decide whether @types/* goes into `dependencies` or `devDependencies`?

I use TypeScript 2 in my project. I'd like to use some js library, but also typings for that library. I can install types with simple npm install @types/some-library. I'm not sure if I should --save or --save-dev them. It …

Read More
TypeScript 2: custom typings for untyped npm module

After trying suggestions posted in other places, I find myself unable to get a typescript project running that uses an untyped NPM module. Below is a minimal example and the steps that I tried. For this minimal example, we will …

Read More
How to resolve: "Definition for rule '@typescript-eslint/consistent-type-assertions' was not found"

My React app is not failing to compile due to the error: Definition for rule '@typescript-eslint/consistent-type-assertions' was not found I'm kind of at a loss. I'm unable to find any current rule definitions in the project. The project …

Read More