Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI support please! #35

Open
zodman opened this issue Apr 21, 2023 · 3 comments
Open

CLI support please! #35

zodman opened this issue Apr 21, 2023 · 3 comments
Labels
new ide request Request for a new ide support

Comments

@zodman
Copy link

zodman commented Apr 21, 2023

tsc --noEmit | pretty-ts-errors

@zodman
Copy link
Author

zodman commented Apr 21, 2023

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

@aarondill
Copy link

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
Copy link
Owner

yoavbls commented Apr 26, 2023

@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

@yoavbls yoavbls added the new ide request Request for a new ide support label Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new ide request Request for a new ide support
Projects
None yet
Development

No branches or pull requests

3 participants