[–] 2 points 3 months ago

This is cool. Back when I worked on Typescript the one type-aware lint you really needed was to prevent boolean coercion. I did get it working but the configuration effort required to get ESLint to have all the right plugins and settings was insane.

  • source
  • [–] 1 point 3 months ago

    i think the first qiestion i have is, what use do you see in this? because... it's a readme file. it's written once, maybe updated when the build process changes, but it's generally static. what's more, it has no required sections, many projects don't need examples, and most things on the big forges don't have links. it's just a freeform document. it doesn't even have to be markdown. rst is pretty common as well, as is plaintext. are you suggesting a tool that can parse a file of unknown format and figure out whether it contains predefined structures?

  • source
  • [–] 3 points 7 months ago

    Wait, is this actually a thing? They really announced a tool called EmDash on April 1st? I fully expected it be be a joke but there's a working playground and actual active GitHub repo and everything

  • source
  • [–] 2 points 8 months ago

    Impressive transition. It's definitely better just to start with type annotations. It's around 3-10x more work to add them later, and you don't get the productivity benefits of having had them along the way. Same goes for Python.

  • source
  • [–] 1 point 1 year ago

    Last updated in December 2024?? This is the web ecosystem we're talking about. Things move fast. I won't read any article written at least 4 months in the future.

  • source
  • I was worried at first when I read they were "reducing" all the documentation comments from new tsconfig files and making users rely on editor autocomplete to somehow find and get the right settings.

    But after looking at their new tsconfig example, it still has all the settings that users care about and looks like what everyone eventually turns their tsconfigs into anyway

  • source