Major Release

[blakeembrey]

Goals:

• Manifest files (Cache typings.json in typings/ directory typings#95)
• Content Addressable Hashes (Content Addressable Hashes #1)
• Warn during install with NPM module (Warn when installing a typing that already has a TypeScript compatible "typings" field typings#9)
• Warn when dependency is not installed (Warning when dependencies are listed but not installed typings#14, requires manifests)
• Error when removing an uninstalled dependency (Warn when deleting a dependency that is not installed typings#15)
• Print info during typings ls (Print "uninstalled", "missing", "extraneous" in typings ls typings#30, requires manifest)
• Resolving .d.ts files correctly (Typings does not support importing type files with multiple '.' in the file name typings#133)
• Keep track of namespaces (warn when installing same dependency as ambient typings#140)
• Installation UX (Improve Typings installation experience typings#144)

Feel free to add things in, but I'll be trying to develop some features for the current iteration while this batch works well as a major release together because it's a pretty big refactoring (and some breaking changes in architecture).

[unional]

• Support module augmentation (Approach for jquery and jquery-plugin type definitions typings#53, Extending a typed package with another typed package typings#168)

something like this?

[blakeembrey]

I'm pretty sure module augmentation is covered with TS 1.8+, but I really need to double check ASAP - https://github.com/Microsoft/TypeScript/wiki/What's-new-in-TypeScript#augmenting-globalmodule-scope-from-modules.

[unional]

Sure. But while it is covered, the generate code need to change so it will work correctly?
I guess supporting global would work, but augmenting others may not when they are nested?

I mean (using chai and chai-http) as example. The generated code:

declare module `chai-http/dist/main` {
  declare module `chai` {
    // augmentation
  }
  ...
}

declare module 'chai-http' {
  export * from 'chai-http/dist/main';
}

or for the hash version:

// typings/.store/hashABC.d.ts
declare module 'chai' {
  // augmentation
}
export ...

// typings/main/chai-http.d.ts
declare module 'chai-http' {
  export * from '../.store/hashABC.d.ts'
}

Would chai be augmented? 🌹

May be I am just not sure about what this mean:

... and are directly nested either your own modules, or in another top level ambient external module

[blakeembrey]

An update - some of these features will likely come out in minors, while content hashing will be 1.0.