{"action":"created","issue":{"url":"https://api.github.com/repos/Microsoft/TypeScript/issues/5097","labels_url":"https://api.github.com/repos/Microsoft/TypeScript/issues/5097/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/TypeScript/issues/5097/comments","events_url":"https://api.github.com/repos/Microsoft/TypeScript/issues/5097/events","html_url":"https://github.com/Microsoft/TypeScript/issues/5097","id":109640119,"number":5097,"title":"Can I package my dependencies typings in a way that snapshots the version?","user":{"login":"alexeagle","id":47395,"avatar_url":"https://avatars.githubusercontent.com/u/47395?v=3","gravatar_id":"","url":"https://api.github.com/users/alexeagle","html_url":"https://github.com/alexeagle","followers_url":"https://api.github.com/users/alexeagle/followers","following_url":"https://api.github.com/users/alexeagle/following{/other_user}","gists_url":"https://api.github.com/users/alexeagle/gists{/gist_id}","starred_url":"https://api.github.com/users/alexeagle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alexeagle/subscriptions","organizations_url":"https://api.github.com/users/alexeagle/orgs","repos_url":"https://api.github.com/users/alexeagle/repos","events_url":"https://api.github.com/users/alexeagle/events{/privacy}","received_events_url":"https://api.github.com/users/alexeagle/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Microsoft/TypeScript/labels/Question","name":"Question","color":"d4c5f9"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-10-03T19:11:48Z","updated_at":"2015-11-18T15:56:43Z","closed_at":"2015-11-13T06:53:22Z","body":"I'm using the new 1.6 module loading for typings from https://github.com/Microsoft/TypeScript/issues/2338\r\n\r\nI distribute my library with NPM and clients pick up the typings for my code magically from the path indicated by the \"typings\" field in the `package.json`. So great! The version of the typings will always match the version of the runtime code.\r\n\r\nBut, one of my files might try to import from a namespace like 'es6-collections'. What version will I pick up, and from where? There is no \"typings\" in https://github.com/WebReflection/es6-collections/blob/master/package.json so I will have to have this file presented to the compiler from the command line, or in the 'files' of my user's tsconfig.json, or a tripleslash ref in the user's code.\r\n\r\nThat means I can tell users to `npm install` my package, but then all my dependencies leak out when I tell them \"now you need to `tsd install es6-collections/es6-collections.correct-version.d.ts`\" and that is not so nice.\r\n\r\nIs there already a way to do without that extra step? I could re-distribute the `es6-collections-correct-version.d.ts` in my NPM package but I don't see a way to depend on it."},"comment":{"url":"https://api.github.com/repos/Microsoft/TypeScript/issues/comments/157758012","html_url":"https://github.com/Microsoft/TypeScript/issues/5097#issuecomment-157758012","issue_url":"https://api.github.com/repos/Microsoft/TypeScript/issues/5097","id":157758012,"user":{"login":"kitsonk","id":1282577,"avatar_url":"https://avatars.githubusercontent.com/u/1282577?v=3","gravatar_id":"","url":"https://api.github.com/users/kitsonk","html_url":"https://github.com/kitsonk","followers_url":"https://api.github.com/users/kitsonk/followers","following_url":"https://api.github.com/users/kitsonk/following{/other_user}","gists_url":"https://api.github.com/users/kitsonk/gists{/gist_id}","starred_url":"https://api.github.com/users/kitsonk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kitsonk/subscriptions","organizations_url":"https://api.github.com/users/kitsonk/orgs","repos_url":"https://api.github.com/users/kitsonk/repos","events_url":"https://api.github.com/users/kitsonk/events{/privacy}","received_events_url":"https://api.github.com/users/kitsonk/received_events","type":"User","site_admin":false},"created_at":"2015-11-18T15:56:43Z","updated_at":"2015-11-18T15:56:43Z","body":"#4913 #5269 #4166 and #5537 it was mentioned in #5657 that there is further movement.  I think the issue is so spread out that it was an effort to consolidate it.  #5537 is likely to be the central ticket that solves this meta problem."}}