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

Plugin not showing after installing #2013

Closed
AlexFreik opened this issue Jun 11, 2022 · 6 comments · Fixed by #2015
Closed

Plugin not showing after installing #2013

AlexFreik opened this issue Jun 11, 2022 · 6 comments · Fixed by #2015

Comments

@AlexFreik
Copy link

AlexFreik commented Jun 11, 2022

I've installed the plugin (macOS Monterey 12.1, VScode 1.66.2). But it seems that nothing has changed. Spell mistakes are still not highlighted, and I don't even have a cSpell icon in the toolbar.

I'm working with a TypeScript .ts file.
Screenshot 2022-06-11 at 11 13 41

I tried to reload the window several times, disabled/enabled the plugin, reinstalled the plugin, plus restarted VS code, but nothing changes.

@AlexFreik AlexFreik changed the title Plugin Not Showing After Installing Plugin not showing after installing Jun 11, 2022
@Jason3S
Copy link
Collaborator

Jason3S commented Jun 11, 2022

@AlexFreik,

Is it possible to update VS Code? The current version is 1.68.0.

If that doesn't work, delete:

~/.vscode/extensions/streetsidesoftware.code-spell-checker*

restart VS Code and install the extension again.

@AlexFreik
Copy link
Author

AlexFreik commented Jun 11, 2022

Is it possible to update VS Code? The current version is 1.68.0.

Oh, now it works, haha) Thanks a lot!

@Lemmingh
Copy link

@Jason3S

There is a mismatch since PR #1995 (v2.2.2), causing this issue.

The vscode-languageclient version 8.0.1 requires VS Code version ^1.67.0:

https://github.com/microsoft/vscode-languageserver-node/blob/8b3c375adc4fa69f63726ef58d911c8e27b261c5/client/package.json#L8

But code-spell-checker still declares ^1.59.1:

"vscode": "^1.59.1"

@Jason3S
Copy link
Collaborator

Jason3S commented Jun 13, 2022

@Lemmingh,

Thank you. I think I patched it in the wrong place.

@Jason3S Jason3S reopened this Jun 13, 2022
Jason3S added a commit that referenced this issue Jun 13, 2022
Jason3S added a commit that referenced this issue Jun 13, 2022
* fix: Fix the needed VS Code version
   fix: #2013
* ci: Adjust the workflows to match VS Code Node Version
@Jason3S Jason3S pinned this issue Jun 14, 2022
@Jason3S
Copy link
Collaborator

Jason3S commented Jun 14, 2022

For those using VS Code older than 1.67.0, please use 2.2.1 version of this extension.

@github-actions
Copy link
Contributor

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants