Go to file
2016-03-23 15:47:28 +01:00
assets fix cli call 2016-02-25 08:26:00 +01:00
compile fix cli call 2016-02-25 08:26:00 +01:00
dist made options handling easier 2016-03-23 15:47:28 +01:00
test/assets now correctly determining release builds 2016-03-23 14:12:58 +01:00
ts made options handling easier 2016-03-23 15:47:28 +01:00
.gitignore now using gulp-typings 2016-03-12 10:21:16 +01:00
.npmignore add optional docs publishing 2016-02-25 08:39:38 +01:00
.travis.yml now completeley hiding git console output 2016-02-23 18:58:44 +01:00
LICENSE Initial commit 2016-01-13 19:21:20 +01:00
package.json 3.6.1 2016-03-23 15:23:14 +01:00
README-dev.md create README-dev 2016-01-16 14:20:14 +01:00
README.md update default behaviour 2016-02-17 05:45:42 +01:00

npmts

Write npm modules with TypeScript without hassle.

Status

Build Status Dependency Status bitHound Dependencies bitHound Code Coverage Status

How to use npmts

Install

First install npmts as dev dependency:

npm install npmts --save-dev

Then use it in package.json's script section to trigger a build:

"scripts": {
    "test": "npmts"
}

Default behaviour

Execution order of tasks

  1. Install typings
  2. Transpile TypeScript with inline sourcemaps
  3. Create Declaration Files
  4. Instrumentalize created JavaScript files with istanbul
  5. Run Tests
  6. Create Coverage report
  7. Upload Coverage reports to travis (must be activated, only triggers on travis)

Typings

npmts looks for ./ts/typings.json by default and installs any defined typings to .ts/typings/. You can then reference the ./ts/typings/main.d.ts file in your TypeScript code.

TypeScript

by default npmts looks for ./ts/*.ts and ./test/test.ts that will compile to ./dist/*.js and ./test/test.js

Use commonjs module system for wiring up files.

Declaration files

npmts also creates an index.d.ts declaration file by default. You can reference it in your package.json like this:

"main": "index.js",
"typings": "./index.d.ts",

Instrumentalize Code

npmts instrumentalizes the created JavaScript code to create a coverage report.

Tests

When Typings have been installed, TypeScript + Declaration files have been transpiled and the resulting JS has been instrumentalized, npmts runs .test/test.js with mocha.

Any errors will be shown with reference to their originating source in TypeScript.

When requiring the module from other TypeScript files, the TypeScript Compiler will use the declaration file to resolve typings.

Custom behaviour

Custom behaviour can be achieved through a config file at the root of your package. The file must be named npmts.json

{
  "mode":"custom",
  "ts":{
    "./customdir/custom.ts":"./customcompiled.js"
  },
  "typings":[
    "./customdir"
  ]
}
  • mode can be "default" or "custom"
  • ts You can list as many TypeScript files as you like. The key represents the source TypeScript file, the value the output file.
  • typings is an array of all direcories that have a typings.json present. Uses the new typings tool from npm.

Readme for Devs

There is a README-dev.md in the repo. This is only of interest for you when looking to contribute to, improve or build upon this package.