• FibreChips
      link
      331 year ago

      Ah yes, node, the JS runtime that very famously doesn’t ever get used with typescript

    • @alokir
      link
      181 year ago

      Typescript is a language, Node is a platform and framework. You can use Typescript in your Node project, they’re not mutually exclusive.

      The way I see it Typescript is more popular than ever, almost all (popular) libraries come with types and every job offer I get they use Typescript.

      And with good reason, our team recently took over a small Javascript app and there are tons of bugs that would never have existed if they were using Typescript. Things like they refactored something but missed to update a reference, or misspelled a variable name, failed to provide a required parameter to a funcrion, referenced a field that existed in another config object etc.

      • @kautau
        link
        5
        edit-2
        1 year ago

        And thankfully we might be getting to a point where TS no longer needs to exist: https://github.com/tc39/proposal-type-annotations

        It’s about time JS gave us the ability to be strict on types, and have that as part of the interpreter as opposed to needing to transpile TS with the overhead involved

    • @[email protected]
      link
      fedilink
      51 year ago

      Managing a node project is like juggling twelve barrels full of monkeys… and those monkeys have rabies. Trying to keep all your dependencies in line is insane.

      • @[email protected]
        link
        fedilink
        21 year ago

        It is absolutely insane to me that people rag on the Python packing ecosystem when TypeScript exists. Sure, Python’s not perfect (Rust and Go seem better, from the small amount I’ve dabbled with them), but way easier and more stable than any TS project I’ve worked on.