VS Code fails to create new Apex Class stub on Windows 11 insider preview version
See original GitHub issueLongtime VS Code user and been using VS Code / SFDX on multiple computers for over a year. I’ve just installed VS Code and the SFDX CLI on a new computer, and now I cannot use the VS Code command palette to create a new Apex Class.
The output I get is:
Trying to copy from a source that does not exist: c:\Users\xxxxxxxxxx\.vscode\extensions\salesforce.salesforcedx-vscode-core-52.4.0\node_modules\@salesforce\templates\lib\templates\apexclass\DefaultApexClass.cls
But what’s funny is that the files do exist (screenshot)
Operating System: Windows 11 (Insider Preview, build 22000.65)
Version: 1.58.0 (user setup) Commit: 2d23c42a936db1c7b3b06f918cde29561cc47cd6 Date: 2021-07-08T06:54:55.083Z Electron: 12.0.13 Chrome: 89.0.4389.128 Node.js: 14.16.0 V8: 8.9.255.25-electron.0 OS: Windows_NT x64 10.0.22000
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
I’m also seeing other SFDX cli command stubs fail. Today it’s failing to run “SFDX: Create Project”. Unlike my original issue, however, the base cli command also fails.
Thanks for confirming @jarodwsams - we actually have one open item to trim spaces at the end of new projects (#3950), but this does seem to be a recurring theme for us resulting in certain mysterious issues 👻 . I’ll bring this up to the dev/docs team and see if there’s anything we can do to prevent these going forward. Cheers!