-
Notifications
You must be signed in to change notification settings - Fork 86
Failed to cache the CSS classes in the workspace for the first time: Cannot read property 'map' of undefined #114
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
Comments
I get the same error message since version 1.20.0 of VSCode. |
Get same on Mac, since VSCode 1.20.0 Anyone on fixing it? |
After updated to 1.20.0,I get this error too. |
Can reproduce this with an empty workspace. |
This happens every time I start Visual Studio Code 1.20. |
Happens here in VSC 1.20.0 on openSUSE Tumbleweed, too. |
same issue
full log: https://pastebin.com/5KTcTwT0 Windows 10, version 1.20.0 of VSCode From looking at your code it looks like "BlueBird" is undefined for some reason: |
There's a bug in the latest version of the API in which calling I will release a new version in a moment. Thanks for the report guys. @Almenon I thought it was Bluebird initially, but it happened a few lines before this map call. |
@zignd I wonder why you cannot use activationEvents like "activationEvents": [
"onLanguage:css",
"workspaceContains:**/*.css"
], |
@jens1o That's actually a great idea. And there's no particular reason, I think the way it is right now is just what came to mind when I created the extension. I will keep that in mind! |
@zignd May I file a new issue for that? |
@jens1o Yup, go ahead. Will help me not forget. Thanks XD |
Insiders 1.20.0.
Intellisense for CSS class names 1.16.1
Windows 10
I get this error any time I open VS Code without a workspace. With a folder/workspace, things work as expected:
Failed to cache the CSS classes in the workspace for the first time: Cannot read property 'map' of undefined
I can click for another attempt, but just get the same error again.
The text was updated successfully, but these errors were encountered: