typings file

The published package is missing the type file nlp.d.ts

Adams-MacBook-Pro-5:nlp_compromise adamjuhasz$ ls -l
total 32
-rw-r--r--   1 adamjuhasz  staff  1080 Jan 27  2016 LICENSE.txt
-rw-r--r--   1 adamjuhasz  staff  4029 Jul  6 07:33 README.md
drwxr-xr-x   4 adamjuhasz  staff   136 Jul 27 08:42 builds
-rw-r--r--   1 adamjuhasz  staff  2626 Jun 20 17:38 changelog.md
-rw-r--r--   1 adamjuhasz  staff  2793 Jul 27 08:42 package.json
drwxr-xr-x  10 adamjuhasz  staff   340 Jul 27 08:42 src

[WorldMaker]

You can let Typescript build unannotated source to start to get an idea of type issues that its type system finds and a feel for the type information that it can inference from your existing code (a more “live” view of what you got from a one-off run of dts-gen for the current typing file). As you add type annotations you can watch it get better (and slowly get the type output better than the current type file giving up with an any as the return of the main function). Typescript supports starting with JSDoc-style type annotations as a first step if you are hesitant to jump straight to Typescript syntax/files.

At that point the type definitions would be a build artifact that directly updates as you update the API, and directly benefits as you JSDoc document the API.

Personally, I think there is a benefit to migrate more fully, more quickly to Typescript. I find it’s much easier to use ES6/ES2015 (and more recent) syntax/tools in Typescript and that Typescript is simpler than Babel to get a good build pipeline to support both ES5 and ES6/ES2015+. Obviously there is some learning curve to that, but it could simplify your build process some, maybe.

[spencermountain]

thank you!