3 ms·
> This release includes plenty of new features, such as our new workflow for getting .d.ts files[0] Does this mean that using Typings is no longer necessary, o
by jameslk 10y ago
> This release includes plenty of new features, such as our new workflow for getting .d.ts files[0]
Does this mean that using Typings is no longer necessary, or is there some additional benefits that Typings still offers?
0. https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-future-of-declaration-files/ https://blogs.msdn.microsoft.com/typescript/2016/06/15/the-f...
- ken47 10y agoTypings is only necessary when you cannot find the d.ts files from http://microsoft.github.io/TypeSearch/ http://microsoft.github.io/TypeSearch/.
- renke1 10y agoAlso, for me it's still unclear how versioning is handled. It always seems like you have to use the latest version of the .d.ts and hope it works with your actual package version.
- DanRosenwasser 10y ago`.d.ts` packages should align on major.minor version numbers, so you'll be able to snap to a version and update appropriately.
- WorldMaker 10y agoTypings is still useful for .d.ts files on package repositories other than NPM (such as directly from GitHub, Bitbucket, etc). Even then, for the moment it has more flexibility for NPM typings than Typescript on its own. Plus, it's still somewhat nice to keep your type definition dependencies in a separate typings.json rather than mixed in with package.json dependencies.