-
Notifications
You must be signed in to change notification settings - Fork 405
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
Develop Against Any Org in Visual Studio Code failing #651
Comments
I suspect you don’t have the right version of the CLI. What are the output of the following in the terminal:
|
Looks like I had to reinstall plugin. It works now. Thanks! |
What are the correct versions? I've tried reinstalling the pre release plugin several times and the pre release commands don't appear in vs code. I'm running sfdx-cli/6.34.0-6fec0d751a (darwin-x64) node-v8.9.4 The appropriate user setting has also been applied. |
The issue I was having in particular was VS Code was out of date. "Check for updates" said I was current which was not the case. After downloading the latest it worked correctly. |
Summary
Short summary of what is going on or to provide context.
I followed this in order to develop against my dev sandbox.
I am getting error with this command and not able to create project.
sfdx force:project:create --projectname kamtest --outputdir /Users/kamlesh.patel/lwc --manifest
▸ Unexpected argument --manifest
Steps To Reproduce:
Follow https://github.com/forcedotcom/salesforcedx-vscode/wiki/Develop-Against-Any-Org-in-Visual-Studio-Code
Run
sfdx force:project:create --projectname kamtest --outputdir /Users/kamlesh.patel/lwc --manifest
▸ Unexpected argument --manifest
Expected result
Should create a project
Describe what should have happened.
Actual result
sfdx force:project:create --projectname kamtest --outputdir /Users/kamlesh.patel/lwc --manifest ended with exit code 1
Describe what actually happened instead.
Additional information
Feel free to attach a screenshot.
VS Code Version:
SFDX CLI Version:
OS and version:
The text was updated successfully, but these errors were encountered: