Josh Pike

that's not really a good enough reason to me. so what if they don't have perfect feature parity? benchmarks are designed to be specific. as a person comparing the two,...

Almost definitely related to https://github.com/rome/tools/issues/4184

Yeah the examples in the link are poor. it’s more like: ‘’’ const x: number = 4; ‘’’ This kind of unneeded type declaration adds noise to the code

just got caught out by something that [switch-exhaustiveness-check](https://typescript-eslint.io/rules/switch-exhaustiveness-check) would have prevented. I think just a simple type checking system capable of unioning literals or something would be plenty... no need...

@Conaclos @ematipico this is becoming a real pain to deal with, it's really hampering our continued ability to use this. latest Rome rage attached ``` CLI: Version: 11.0.0-nightly.97e48b4 Color support:...

is there a way I can just run it with some sort of profiling enabled and have the logs dump as they happen? I wouldn't have the slightest clue how...

Ok good news, I can get it to stall on a particular file I have. But Rome and Rome Trace panels in VSCode tell me nothing. What next?

More useful info: if I run `rome check` or `rome ci` on that same file, it runs fine and doesn't get stuck. This seems to be specific to the language...

OK so looks like it was't one file in particular, it just decides at some arbitrary point to start playing up. Rome output terminal says nothing: ``` [cli-stdout] data 84...

 This happens when I try to just quit VSCode, whatever Rome's doing it's also blocking VSCode. Terminating the Rome process directly allows VSCode...