Closed cantide5ga closed 8 years ago
@types
with definitions from our registry. You should just be able to continue using Typings or TypeScript 2.0 as is without any issue.There's also https://github.com/typings/typings/issues/600 which you may be interested in.
I have a handful of type definitions (some converted from DT) that embrace the use of external modules that was a huge selling point when typings got started. I'm starting a new project and this is my first opportunity to get in sync with Typings 2.0's support for installing type definitions. I spent a fair amount of time getting caught up on everything, but everything is still a bit disjointed. I got some questions/musings:
npm install @types/react
, which pulls a migrated definition from the old DefinetlyTyped. With typings,typings/registry
was the preferred repo.typings/registry
takes precedence over what@types
is using? Especially considering that a handful of PR's to fix/update some definitions only had the registry definitions in mind - not those in DefinetlyTypedtypings/registry
with Typescript 2? Btw, how would I do that now?I'm very patient and excited to see this all become 'standardized' in a way; I have no strong opinions and am along for the ride :) but, it's always been a bit painful. Thanks for any thoughts.