3 ms·
For the average developer, does this mean we can simply ugprade to typescriptn 7 and start enjoying the improvements?
by perrohunter 4mo ago
For the average developer, does this mean we can simply ugprade to typescriptn 7 and start enjoying the improvements?
- lelandfe 4mo agoIf you’re continuing to use the previous version in CI, there’s no reason to not use this locally. It’s a tremendous speed upgrade.
- herpdyderp 4mo agoThe reason to not use it locally is false negatives or false positives compared to your CI version. Your local tsc will not match the results of your CI tsc.
- sheept 4mo agoIt depends, but for larger projects, you might have tooling for TypeScript that relies on its API, which isn't available in TS 7.0.
- herpdyderp 4mo agoDepends on your tooling. I can't update yet due to ESLint package dependency mismatches. I'll have to wait for all the ESLint plugins to update. There may also be new failures in your code from the v6 to v7 update. I had only a very minor one though in my initial test.
- dmix 4mo agoEslint is like an anchor on upgrading anything (including Eslint itself). I'll be happy to move on from it.
- Timon3 4mo agoI've been really, really happy with oxlint. It has all the rules I usually need and the configs etc. tend to just work, whereas I don't know how much time I spent getting ESLint to work in slightly more complex repo setups.