Skip to content

Fixing 'no such file or directory' error when using workspaceFolder - #89

Closed
Christopher Roach (croach) wants to merge 1 commit into
microsoft:masterfrom
croach:master
Closed

Christopher Roach (croach) wants to merge 1 commit into
microsoft:masterfrom
croach:master

Conversation

@croach

@croach Christopher Roach (croach) commented Sep 30, 2017 •

Copy link
Copy Markdown

Loading the extension created by the yo code command results in the following error:

[${workspaceFolder}]: Error: ENOENT: no such file or directory, scandir '${workspaceFolder}'

This happens because the workspaceFolder environment variable used in the multiple instances of launch.json does not exist (no longer exists?). The documentation suggests that workspaceRoot variable is what should be used. This commit switches all instances of workspaceFolder to workspaceRoot to fix issue #88.

The `workspaceFolder` environment variable used in the multiple
instances of launch.json does not exist (no longer exists?). The
[documentation][1] suggests that `workspaceRoot` variable is what
should be used. This commit switches all instances of
`workspaceFolder` to `workspaceRoot`.

[1]: https://code.visualstudio.com/docs/editor/tasks#_variable-substitution
@msftclas

Microsoft Contribution License Agreements (msftclas) commented Sep 30, 2017 •

Copy link
Copy Markdown

CLA assistant check
All CLA requirements met.

@aeschli

Copy link
Copy Markdown
Collaborator

Thanks for pointing to this, we published that change to early. ${workspaceFolder} will be available in 1.18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants