TypeScript Definition manager for DefinitelyTyped
TypeScript Definition manager for DefinitelyTyped
- It is recommended you check-in the definitions you install into your VCS.
- Don't forget to move your fixes back to DefinitelyTyped
The Github API has a 60-requests-per-hour rate-limit for non-authenticated use. You'll likely never hit this as TSD uses local caching and the definition files are downloaded from Github RAW urls. Optionally a scope-limited Github OAuth token can be used to boost the limit to 5000.
The CLI tool tracks some anonymous usage statistics about what definitions are installed though TSD in Google Analytics (using universal-analytics). There is also a update-notifier service to check for TSD updates.
$ npm install tsd -g
For previews and history check the release tags.
$ tsd -h
Sometimes it looks like this:
Create a new
$ tsd init
Minimal query for
$ tsd query d3
Tip: if you are using Linux or Mac OS X, use
$ tsd query "*".
Get some info about
$ tsd query jquery --info --resolve$ tsd query jquery -i -r$ tsd query jquery -ir
$ tsd query */jquery.*
$ tsd query mocha --history$ tsd query mocha -y
$ tsd query *
pixi definition on github:
$ tsd query pixi --action browse$ tsd query pixi -a browse
$ tsd query gruntjs --action visit$ tsd query gruntjs -a visit
sinon definitions all at once:
$ tsd query mocha chai sinon --action install$ tsd query mocha chai sinon -a install
$ tsd query bootstrap --action install$ tsd query bootstrap -a install
Solve the reference to
jquery, overwrite existing files and save to the tsd.config:
$ tsd query angular --resolve --overwrite --save --action install$ tsd query angular -r -o -s -a install$ tsd query angular -rosa install
Install and save to
$ tsd query mocha chai -r -o -s -a install -b test
TSD uses a (globbing) path + filename selector to query the DefinitelyTyped index. The results can then be modified using various filters:
Note how the definition filename takes priority:
$ tsd query module$ tsd query project/module
For example, consider these definitions:
Notice the pattern, and ignore the
Select definitions using only the module name:
$ tsd query module$ tsd query module-addon
Or use a selector derived from the path format:
$ tsd query project/module$ tsd query other/module
The selector also supports globbing, for example:
$ tsd query project/*$ tsd query project*$ tsd query module*$ tsd query project/module*$ tsd query project-*/plugin*$ tsd query *project*/*$ tsd query project/plugin*$ tsd query other/module$ tsd query */module$ tsd query */module-*$ tsd query */*plugin
Globbing implements only leading and trailing (for now).
Note: the semver postfix of definition files is expected to be separated by a dash and possibly a
If there are multiple matches with same module name they will be prioritised:
- The unversioned name is considered being most recent.
- Then versions are compared as expected following these comparison rules.
- Use the
-voption to set a semver-range:
$ tsd query node -v latest$ tsd query node -v all$ tsd query node -v ">=0.8 <0.10"$ tsd query node -v "<0.10"
-d option to set a date-range (find dates using
$ tsd query d3 --history$ tsd query d3 --date ">=2012-01-01"$ tsd query d3 -y$ tsd query d3 -d "<2012-01-01"
-c option to supply sha1-hash of a commit (find a commit hash using
--history), for convenience a shortened sha1 hash is supported.
$ tsd query youtube --history$ tsd query youtube --date d6ff$ tsd query youtube -y$ tsd query youtube -c d6ff
- For now this only works with commits that actually changed the definition file you selected (eg, listed in
--history) This will be expanded to allow selecting from any commit at a later date.
var tsd = require'tsd';var api = 'path/to/tsd-config.json';apisearch'jquery/*'then// yesutilinspectres;// no;
For a practical example see grunt-tsd.
Note: Keep in mind this project started as a
<reference> style TypeScript
v0.8.x single-file compile target, which makes it harder to limit the exported API compared to
import multi-file style. This is also why the definitions include more then just the
API export is somewhat experimental; take care to lock versions and test on upgrade. If you plan to use TSD as module in a tool or project then feel free to leave a message and coordinate stuff.
tsd.json file is automatically created in the root of each project: it configures TSD and it tracks the definitions that are installed (using
--save). See the JSON Schema for more info.
tsd.d.ts file links every definition that is installed (with
--save) for convenient reference:
/// <reference path="../typings/tsd.d.ts" />
By default it is created in the typings folder but it is configurable in
tsd.json. TSD will check the existing references and respects re-ordering.
This is a optional JSON encoded file to define global settings. TSD looks for it in the user's home director (eg:
%USERPROFILE% on Windows,
~ on Linux), and in the current working directory.
- "proxy" - Use a http
Any standard http-proxy as supported by the request package.
- "token" - Github OAuth token:
The OAuth token can be used to boost the Github API rate-limit from 60 to 5000 (non-cached) requests per hour. The is token needs just 'read-only access to public information' so no additional OAuth scopes are necessary.
You can create this token on Github.com:
- Go to https://github.com/settings/tokens/new
- Deselect all scopes to create a token with just basic authentication.
- (verify you really deselected all scopes)
- (wonder why these presets were set??)
- Enter a identifying name, something like "
TSD Turbo 5000"
- Create the token.
- Copy the hex-string to the
tokenelement in the
- Verify enhanced rate-limit using
$ tsd rate
Change or revoke the token at any time on https://github.com/settings/applications
Note: keep in mind the
.tsdrc file is not secured. Don't use a token with additional scope unless you know what you are doing.
The bare 'no scope' token is relatively harmless as it gives 'read-only access to public information', same as any non-autenticated access. But it does identify any requests done with it as being yours, so it is still your responsibility to keep the token private.
Of course! The official plugin is grunt-tsd.
If TSD is used in a way that needs many unique API calls in a short period (like using
--history on big selections), or shares an internet-connection with multiple users (like in an office) then the rate limit blocks the API. It blocks for 60 minutes after the first request of the total 60.
For these cases TSD has an option to use a Github OAuth token and raise your local rate-limit from 60 to 5000 per hour. See the
.tsdrc-section elsewhere in the readme.
v0.5.7 there are two ways to configure the location of the proxy server:
- Use a environment variable. TSD support the conventional fields: pick one of
- Use a global
.tsdrcfile and set a
proxyvalue (see the tsdrc-section elsewhere in the readme).
The old TSD
v0.3.0 had it's own repository data file that mapped module names to url's of definition files. This had a few downsides for (maintenance being one). Since
v0.5.0 we link directly to DefinitelyTyped where the directory and file names are a reasonable indicator but not 100% identical to the names as you'd find them in npm, bower or other package managers.
The DefinitelyTyped group is working on a meta-data source that will solve this.
Yes, and no (and later yes again)
There is basic support for parsing semver-postfixes from the definition file names, and you can filter on this using semver ranges with the
--version option: Try it with the 'node' definitions.
It works well but is not used much in the current DefinitelyTyped repository. The DefinitelyTyped group is working on a meta-data source that will solve this (the Nuget exporter is waiting for this too).
The cache is stored in the users home directory (like
$ npm). Use
$ tsd settings to view the current paths. Use the
--cacheDir to override the cache directory, or
--cacheMode to modify caching behaviour.
See the release tags fore more details.
current- Full rewrite by @Bartvds: drops the separated TSD data registry in favour of using the Github API to pull definitions directly from DefinitelyTyped.
- Original version by @Diullei.
v0.3.x (old readme here):
$ npm install firstname.lastname@example.org -g
Some essential modules used to build TSD:
- es6-shim & weak-map - Map, Sets and some usefull things.
- grunt-ts - TypeScript compiler for grunt.
- tslint + grunt-tslint - TypeScript linter (contribute some rules!)
- gruntfile-gtx - Gruntfile powerbooster (by author).
- tv4 - JSON-Schema validation like a boss.
- q and q-io - Promises as promised.
- semver - Semver parsing and filtering
To rebuild clone or fork the repos:
$ npm install
Build, lint and test
$ grunt test
Only rebuild (and run cli)
$ grunt build
Either install global or use in dev folder:
Run in dev folder
$ node ./build/cli.js query d3 --dev
Install to global cli
$ npm install . -g
TSD uses gruntfile-gtx to test separate test suites sets during development:
$ grunt -h
Example: run only api tests
$ grunt gtx:api$ grunt gtx:cli$ grunt gtx:tsd
It is recommend you use an intelligent parsing IDE (WebStorm or VisualStudio) and a big screen (or two) on a properly powerful workstation.
Code looks best with tabs rendered at 4 spaces (3 is nice too, or 6 or 8.. I don't really care, because smart-tabs are awesome like that). The gruntfile uses slightly harsh JSHint and TSLint settings to enforce code style, but there is an
.editorconfig to elevate some of the pain.
Contributions are very welcome; please discuss larger changes in a ticket first. Fixes and simple enhancements are always much appreciated.
Note: Contributions on the definition files go directly to DefinitelyTyped.
The TSD CLI tool collects definition usage information, like the queries made to the repo and the definitions that get installed. The information collected amounts to about same level of detail as services like npm or github would collect (maybe even less as we don't track a user id).
The API does not track anything.
The optional Github OAuth token is only used to authenticate with the Github API. The token is not stored anywhere but the local machine. It is your responsibility to keep your token safe.
Using an OAuth token with additional scope is not advised nor supported (even though it could make TSD work with private repositories). But it might also leak repo or content names to analytics or leave a bare http cache in your temp dir. If this bothers you please review the license and/or leave a message.
Changes to the policy should be announced in release notes, and ideally ask confirmation on the first CLI use.
Copyright (c) 2013 by Bart van der Schoor.
Licensed under the Apache License, Version 2.0.
- note: there is some imported MIT licensed code by myself, Bart van der Schoor
Copyright (c) 2012 by Diullei Gomes.
Licensed under the MIT License.