Randy Hudson

Yes, I can reproduce this easily in several workspaces. I ran extension bisect and it identified this extension (which I had already determined manually). If I try to reproduce in...

It happens: - in the `master` branch - in branches that have been pushed (regardless of whether a PR exists) - in branches that only exist locally

I have this extension installed: `alefragnani.separators` If I disable this extensions (but keep all my others enabled), the problem goes away. However if I enable ONLY this extension and yours,...

@hardfist here's an example repo: https://github.com/dinofx/rspack-unstable-identifiers/tree/main Just run `pnpm i` and `pnpm run build`. `build-1` and `build-2` are identical copies of the same package, with two copies of the same...

``` 1 satisfies number; ``` is transpiled to: ``` 1; ``` This is clearly an unused expression (and odd use of `satisfies`).

Both the `default:` and the unused expression are unreachable/dead runtime code. You can simply use https://typescript-eslint.io/rules/switch-exhaustiveness-check instead

Regardless of preferred coding styles, this isn't really subjective. `thing satisfies never;` is objectively an unused expression, no different than the [other 3](https://github.com/typescript-eslint/typescript-eslint/pull/8668). It sounds like some folks would like...

> the other three that are unused both at runtime and at typechecking time