News for hackers. Stuff that matters.
Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by sanitycheck on Friday December 15, 2023 @08:37AM (#38654040)
I think if my CI was taking 45 mins to lint I'd look at linting only the files changed since the previous build instead of splitting it across 40+ workers. Or writing a new linter in Rust.

But I'm generally working in a (human & financially) resource-constrained environment.

Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by arp242 on Friday December 15, 2023 @12:16PM (#38656187)
One problem is that a change in a.js may trigger a new error in b.js.

ESLint could also cache things fairly trivially:

  hash = hash_file_contents()
  if previously_seen_hashes.contains(hash)
      report_previous_results()
  else
      run_lint_and_cache_results()
  end
maybe that already exists. But that has the same problem.

When you've got enough hardware to throw at it, then "just run it on the full code" is the safest.

Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by throwup238 on Friday December 15, 2023 @09:46AM (#38654675)
Typescript lints are type-aware so you can’t just lint changed files, you have to relint the entire codebase to check if any type changes have impacted the unchanged code.
Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by pcthrowaway on Friday December 15, 2023 @10:11AM (#38654911)
Wouldn't an issue with a type change be caught at typescript compile/check steps?

I'm not aware of eslint rules which would complain about some other untouched file if types have changed in ways such that the program still compiles

Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by anamexis on Friday December 15, 2023 @10:32AM (#38655101)
Re:Oxlint – written in Rust – 50-100 Times Faster than ESLint by Too on Saturday December 16, 2023 @02:40AM (#38662525)
Is there no incremental lint mode? When developing you need that for instant feedback, same mechanism should work for CI.