3 ms·
Last time I tried TypeScript we ended up abandoning it after having mismatches between dependencies and TS definitions. We had to postpone upgrading libraries
by jacobr 10y ago
Last time I tried TypeScript we ended up abandoning it after having mismatches between dependencies and TS definitions.
We had to postpone upgrading libraries to wait for definition updates or write and maintain them ourselves. This was in the early stage of a project though, we needed to get a quick first version out in 2 weeks and it just wasn't worth the hassle.
Has this situation improved - I understand typings are no longer installed with a 3rd party tool/registry?
- simooooo 10y agoThey aren't? How does it validate the code without typings for everything
- Ciantic 10y agoThere is one significant change with TS 2.2, you don't have to use type definitions for libraries anymore. Since all JavaScript is valid TypeScript. With out of the box setup the import from library that has no type definitions, works just fine. It returns `any` type, so you can use all libraries just like you would in JavaScript. So if you ram your head against bad type definition of a module, just delete it and continue using it like you would in normal JS.