3 ms·

Forced Typescript, not thinking about what runtime I’m installing the package to, and automatically generated documentation sounds pretty compelling. If they c

• steve_rambo 3y ago
  I worked on a project with "forced typescript" and poor code review practices (since fixed). It ended up with overuse of `any` and all the same problems you run into in a pure JS codebase. I had to fix most of that which was a massive undertaking. Whoever wants to (and knows how to) use typescript already use it without being forced to. I don't think other people will benefit from that at all.
  • Aeolun 3y ago
    Eh, I feel like there’s some part of the JS community that gets a kick out of snubbing Typescript entirely, so when I import those packages I get to provide my own types. I just don’t want to facilitate that, so a ‘TS only’ repository would save me the trouble. Like, it’s not a huge issue, but I just don’t want to spens the time thinking about that stuff.
    • forty 3y ago
      I don't understand. It you don't want to use packages without types, cannot you do just that already? I guess if you have to use package without typing it's because no good alternative with typings exists, which I'm not sure how creating a separate community will help with