CLI support please!

[zodman]

tsc --noEmit | pretty-ts-errors

[zodman]

Doing the cli you will kill #26 #21 and support others ...

[aarondill]

Perhaps a cli flag... for ease of use, the default would be this, but something like pretty-ts-errors --lsp would follow the LSP protocol, allowing 26, 21, and other ide requests.

Then again, you may get a one-size-fits-all senario, and perhaps this would be better to be in a separate application.

I personally prefer the LSP support than this, however, I can see the appeal here, and can support this provided it doesn't restrict the potential LSP support.

[yoavbls]

@zodman I'm not sure it will solve #26 and #21, but I agree it will be helpful and lsp it's the path for that.
@johnsoncodehk already did a POC of that in volar.
I'm working now on moving to a monorepo and publishing the core functions as packages. It'll allow the community to collaborate and support other platforms like Neovim, cli, etc

[crrobinson14]

I would take any and all loss of functionality to be able to run this at the command line because I'm not a VSCode user. I have no oranges. :) If I get 10 oranges instead of 12 I will still enjoy that juice very much!

[voxpelli]

I created a CLI for this: https://github.com/voxpelli/pretty-ts-errors-cli

In addition to pretty printing directly in the terminal it also contains an option to generate markdown, so that one can easily copy and paste a pretty error to eg. a GitHub issue