-
Notifications
You must be signed in to change notification settings - Fork 35
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
can't use linter in 2.20 #140
Comments
Same here. Downgrading to 2.0.1 fixed the issue. |
OK, I must have messed up something while publishing, I'll take a look, thanks. |
As a temporary fix for this issue, you can do the following:
From what I could tell, this is an issue with the bundling of the new dependency When VSCode tries to activate the extension it encounters the following error:
However, I do not think that this is an issue with
And as can be seen in the log, there are multiple entries that mention files from I hope this helps with fixing the issue. |
@Gimly , it looks the extension hard errors on every load w/ version 2.20 because of this missing dependency. Syntax highlighting gets loaded but downstream things break. Any ETA on a fix for this? |
Last couple of weeks were a little crazy and I wasn't able to work on that. I'm not so sure about this week either. I'll do my best. Really sorry. |
@sndst00m any thoughts on what may be going wrong here? The missing dependency is your new vscode-textmate-languageservice so any insight would be appreciated. Maybe there's something special about how it should be depended on? |
I don't believe so, and I'm also unable to reproduce |
Curious. If you open the Output window and go to "Log (Extension Host)" and scroll around, you don't see the errors that @mjdshibly reported? I reliably see those. Syntax highlighting works, but the other providers are then broken. Some other folks I work with have reported similar issues. |
@sndst00m Did you make sure that your installation of the extension is completely clean, and that you're not running the development version in an Extension Host window? |
Happened when I deleted the |
This should be generated using https://github.com/SNDST00M/vscode-native-svg-preview/blob/v1.60.2/package.json#L201-L204 |
I've pushed a new version which should hopefully fix that issue. Reopening until I have confirmation it is indeed fixed. |
I'm glad to see this new version has fixed the bugs recently mentioned, but "Peek Defination" still cannot work when I put the function into the same folder. It says "No definition found". |
Something's gone catastrophically wrong in the TM-based language service again.
In the backend it reads off the document symbol provider just like the "go to symbol" feature. Those two providers work, so I'll have to debug. |
Now fixed! Full steam ahead with a publish definitely coming soon™ |
Hi these issues have been addressed in the latest version! Please notify us if not |
#174 allows us to officially use the bundler again.. In particular we have the confidence that we are not depending on Node modules or modules invoked from VS Code itself (which the core team have actively endeavoured to prevent etxdevs from using). |
No description provided.
The text was updated successfully, but these errors were encountered: