3 ms·
I have some additional genuine questions: * How would scoped modules' (@scope/name) typings be named in this convention? * How do the version of these new typ
by filearts 10y ago
I have some additional genuine questions:
* How would scoped modules' (@scope/name) typings be named in this convention?
* How do the version of these new typings modules correlate to versions of the underlying modules? In other words, how can I access the typings for the previous major of lodash from which breaking changes emerged?
- RyanCavanaugh 10y agoThe major and minor version of the types modules corresponds to the version of the underlying package; the patch version will increment when the type definition changes. We're still figuring out what to do with scoped packages in this scheme. Most likely we'll end up with a single types package for everything under a specific scope, since that's what people seem to be using scoped packages for. They're pretty rare so far so this is kind of TBD.
- softawre 10y agoFor clarity, can you give an example of how to `npm install` an old version of lodash such that we get the old version of the lodash.d.ts?
- DanRosenwasser 10y agoAssuming it was published, `npm install @types/lodash@2.0.1`.