Is there a way to add typescript definitions (.d.ts files) to a pure javascript project directly (e.g. in package.json). I can't find any documentation on that.
-
interesting question :) I will just follow.mihai– mihai2016-05-13 12:29:01 +00:00Commented May 13, 2016 at 12:29
Add a comment
|
2 Answers
There is a page in the TypeScript Handbook on adding typings to an NPM Package. I'll copy and paste here:
Typings for NPM Packages
The TypeScript compiler resolves Node module names by following the Node.js module resolution algorithm. TypeScript can also load typings that are bundled with npm packages. The compiler will try to discover typings for module
foousing the following set of rules:Try to load the package.json file located in the appropriate package folder (
node_modules/foo/). If present,read the path to the typings file described in thetypingsfield. For example, in the following package.json, the compiler will resolve the typings atnode_modules/foo/lib/foo.d.ts{ "name": "foo", "author": "Vandelay Industries", "version": "1.0.0", "main": "./lib/foo.js", "typings": "./lib/foo.d.ts" }Try to load a file named
index.d.tslocated in the package folder (node_modules/foo/) - this file should contain typings for the package.The precise algorithm for module resolution can be found here.
Your definition files should
- be
.d.tsfiles- be written as external modules
- not contain triple-slash references
The rationale is that typings should not bring new compilable items to the set of compiled files; otherwise actual implementation files in the package can be overwritten during compilation. Additionally, loading typings should not pollute global scope by bringing potentially conflicting entries from different version of the same library.
7 Comments
Drew Noakes
Seems it should be
types not typings.Drew Noakes
Thanks for the back story. All current examples online use
types. If you haven't already, consider updating your answer.
CoderDake
Nice seinfeld Reference.
rgvassar
I have not changed the field from "typings" to "types" because the current documentation says that they are synonymous. We have another answer that uses "types". I prefer to have two different answers that both work, rather than two answers that have been edited to be the same.
|
Visual Studio 2015 will not recognize the definition file unless you use the types property in package.json
https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html
{
"name": "awesome",
"author": "Vandelay Industries",
"version": "1.0.0",
"main": "./lib/main.js",
"types": "./lib/main.d.ts"
}
*You will have to use the three slashes include reference path in your ts files.
/// <reference path="../node_modules/../lib/main.d.ts" />
For anyone else landing here & wanting to link types to their npm package, a handy tutorial that might help!
