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

How to reference the parent directory of the ${workspaceRoot} in tasks.json command? #22140

Closed
stefan2410 opened this issue Mar 7, 2017 · 1 comment
Assignees
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code) tasks Task system issues

Comments

@stefan2410
Copy link

I have asked this question also in stackoverflow

I have installed the node_modules in the parent directory of a group of related JavaScript ES6 projects with common configuration.
Each one with its workspace, in VSCode.
I did not find yet a way to reference in the tasks.json a directory above ${workspaceRoot}.
But if I set in the tasks.json of every project, in the "command": the absolute windows path with the node_modules, everything works fine.
webpack, babel-loader, hot reload.
Is there a way from VSCode enviroment to set the parent directory of the ${workspaceRoot} ?

thanks

@ramya-rao-a ramya-rao-a added the tasks Task system issues label Mar 7, 2017
@dbaeumer dbaeumer added the *question Issue represents a question, should be posted to StackOverflow (VS Code) label Mar 7, 2017
@dbaeumer
Copy link
Member

dbaeumer commented Mar 7, 2017

I would think ${workspaceRoot}/../dir should do the trick. t may be I misunderstand the questions since it looks to easy. If not, can you make an example with a directory structure.

@dbaeumer dbaeumer closed this as completed Mar 7, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*question Issue represents a question, should be posted to StackOverflow (VS Code) tasks Task system issues
Projects
None yet
Development

No branches or pull requests

3 participants