-
Notifications
You must be signed in to change notification settings - Fork 262
Where should maintainers put their definition files? #639
Comments
If you're comfortable with DefinitelyTyped, you can continue to maintain them there. If you're asking why Typings also has a definition, it's just easier for people to maintain. The reason Typings exists is to make it easier to consume, publish and manage type dependencies. Having a mono-repo makes it very hard for a maintainer to maintain their definition. So currently |
@blakeembrey Okay I see. Thanks for your answer. I actually prefer the way Typings handles the definitions. It just seemed like DefinitelyTyped was a lot more active than the typings registry, which got me confused. But good to know we're working on a way to standardize this process. |
@blakeembrey apologies for missing the discussion around the merge. Is there a timetable for this and any protocol for handling conflicts where the package exists in both repos? |
@akeating Waiting for microsoft/types-publisher#4. On conflicts, I'm not sure what to suggest - there's a reason people use the Typings structure as maintainers (myself included). It makes it easier on us and avoids the bundle of deserted definitions that is DefinitelyTyped, so I imagine Typings will continue to exist until Microsoft can support redirects and we can contribute to |
Hello, I maintain the mongoose definitions for DefinitelyTyped.
I noticed these typings could appear in multiple places:
more...?
Is there currently 1 preferred place to put my Typescript Definitions?
Or should I maintain the definitions across all of these places?
The text was updated successfully, but these errors were encountered: