JSPM – typings@0.8.1

Package Exports

typings

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (typings) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

The TypeScript Definition Manager.

Updating from 0.6 to 0.7? Make sure you rm -rf typings/ and re-install them, the directory structure has changed.

Quick Start

# Install Typings CLI utility.
npm install typings --global

# Search for definitions.
typings search tape

# Find an available definition (by name).
typings search --name react

# Install ambient typings (default from "DT", configurable through `defaultAmbientSource` in `.typingsrc`)
typings install mocha --ambient --save

# Install non-ambient typings (default from "npm" registry, configurable through `defaultSource` in `.typingsrc`)
typings install chai --save

# Install typings from particular registry
typings install env!atom --ambient --save
typings install npm!bluebird --save

# Use `main.d.ts` (in `tsconfig.json` or as a `///` reference).
cat typings/main.d.ts

Usage

Typings is the simple way to manage and install TypeScript definitions. It uses typings.json, which can resolve to GitHub, NPM, Bower, HTTP and local files. Packages can use type definitions from various sources and different versions, and know they will never cause a conflict for users.

typings install debug --save

A public registry is maintained by the community, and is used to resolve official type definitions for JavaScript packages.

Contributing

# Installation
# Fork this repo (https://github.com/typings/typings)
# Clone the fork (E.g. `https://github.com/<your_username>/typings.git`)
cd typings

# Install modules
npm install

# Build
npm run build

# Test
npm run test

License

MIT

typings