Dependencies
All dependencies are managed by npm. Make sure all the declaration packages you depend on are marked appropriately in the "dependencies"
section in your package.json
. For example, imagine we authored a package that used Browserify and TypeScript.
{ "name": "browserify-typescript-extension", "author": "Vandelay Industries", "version": "1.0.0", "main": "./lib/main.js", "types": "./lib/main.d.ts", "dependencies": [ "browserify@latest", "@types/browserify@latest", "typescript@next" ] }
Here, our package depends on the browserify
and typescript
packages. browserify
does not bundle its declaration files with its npm packages, so we needed to depend on @types/browserify
for its declarations. typescript
, on the other hand, packages its declaration files, so there was no need for any additional dependencies
Our package exposes declarations from each of those, so any user of our browserify-typescript-extension
package needs to have these dependencies as well. For that reason, we used "dependencies"
and not "devDependencies"
, because otherwise our consumers would have needed to manually install those packages. If we had just written a command line application and not expected our package to be used as a library, we might have used devDependencies
.
Please login to continue.