I find myself facing a similar question to the one posed here:
My NPM Package, typed-lexer, includes a d.ts file and its corresponding entries in the package.json file. When I consume this package in a regular node.js app using npm install and tsc --init, everything works smoothly - both my IDE (Visual Studio Code) and the compiler can locate the type definition file for typed-lexer.
However, things take a turn for the worse when I install my package via jspm. Since the d.ts file is an external declaration file (lacking a declare module), I am unable to simply reference it with <reference ... />
. Installing the package through both jspm and npm improves the IDE support but falls short when it comes to the browser where TypeScript files are compiled.
Given that the previous question remains unanswered and considering the recent release of typescript 1.8, I am seeking solutions for this issue. My current setup involves jspm 0.17.0-beta.12 and typescript 1.9.0.