Skip to content

fix: lsp server errors if vscode-eslint cant be extracted #1933

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

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

jamesgibbons92
Copy link

Otherwise the fs calls will fail as directory doesn't exist and it litters the tui output with errors

Otherwise the fs calls will fail as dir doesn't exist
@jamesgibbons92
Copy link
Author

fixes this

image

@jamesgibbons92
Copy link
Author

jamesgibbons92 commented Aug 14, 2025

also this should probably be updated to use js zip, it assumes you have unzip installed - I did try but there was some issues with symlinks not being extracted properly so gave up

@rekram1-node rekram1-node requested a review from thdxr August 14, 2025 16:26
@jamesgibbons92 jamesgibbons92 changed the title fix: bail if vscode-eslint cant be extracted fix: lsp server errors if vscode-eslint cant be extracted Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant