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

Error message "command 'cake.intellisense' not found" #92

Closed
JorisMolnar opened this issue Jul 2, 2018 · 7 comments
Closed

Error message "command 'cake.intellisense' not found" #92

JorisMolnar opened this issue Jul 2, 2018 · 7 comments
Labels
Milestone

Comments

@JorisMolnar
Copy link

Today I received an update to the Cake extension for Visual Studio Code.

After this update, when I run any of the Cake commands in VS Code, I get the following error message (dependent on the command):

command 'cake.commandname' not found

If I open the Developer Tools of VS Code I can see the following errors in the console log:

image
VisualStudioCodeDevToolsCakeError.log

I've confirmed with a colleague that it was working before the new version of the cake extension got installed.

@pascalberger
Copy link
Member

This is a known issue with the packaging of the latest version of the extension and we're currently working on a fix.

In the meantime you can try the following:

  • Close Visual Studio Code
  • Open Command Prompt
  • Navigate to C:/Users//.vscode/extensions
  • Navigate to the Cake extension folder for version 0.11.1
  • Run npm install
  • Re-open Visual Studio Code

@gep13
Copy link
Member

gep13 commented Jul 2, 2018

@JorisMolnar on a side note...

Where did you find that Developer Tools for VS Code window? I was hunting for that this morning, but I couldn't find it 😄

@JorisMolnar
Copy link
Author

@gep13 Right here 😊

image

@gep13
Copy link
Member

gep13 commented Jul 2, 2018

Doh! I looked through every other menu, apart from this one!!

Thank you very much!

@gep13 gep13 added this to the v0.11.2 milestone Jul 2, 2018
@gep13 gep13 added the Bug label Jul 2, 2018
@gep13 gep13 closed this as completed Jul 2, 2018
gep13 added a commit that referenced this issue Jul 2, 2018
- Ultimately, this came down to a problem with a missing dependency
- The ini package
gep13 added a commit that referenced this issue Jul 2, 2018
* hotfix/0.11.2:
  (GH-92) Fixing problem with packaging
@gep13
Copy link
Member

gep13 commented Jul 2, 2018

@JorisMolnar thank you very much for taking the time to post this issue. Your original screenshot directed me to exactly the cause of the problem. I have just pushed out a new version of the extension, 0.11.2, which should correct the problem. Please let us know if you continue to see issues.

gep13 added a commit that referenced this issue Jul 2, 2018
* hotfix/0.11.2:
  (GH-92) Fixing problem with packaging
  (build) Does this work?
  (build) Testing appveyor
  (build) Remove cache folder
  (build) test. test. test
  (build) testing
  (build) Moar testing
  (build) Moar testing
  (build) Testing build with tsc
  (GH-90) Updating to latest vsce
@Lakkanna
Copy link

check .vscodeignore make sure that it's not containing node_modules, if exists remove node_modules from .vscodeignore

@ronilaukkarinen
Copy link

@Lakkanna You are a lifesaver! I literally bashed my head to the wall 4 hours with this... published my first vscode plugin and kinda new to it, after hours of googling I finally found your answer. I don't know what node_modules was to do in .vscodeignore but I'm glad I finally got this solved. So thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants