Reputation: 828
I'm not very familiar with vscode tasks but I want to automate one tiny thing. Everytime I open my editor, I need to run 4 commands:
cd client
npm start
cd server
npm run dev
I'm just looking for a way to automate this.
Upvotes: 1
Views: 1457
Reputation: 11819
There is currently no support for running a task when VS-Code is opened, however; VSCode added support, roughly 2 years ago, for running a task when a directory is opened.
This is what the configuration property looks like:
// THIS EXAMPLE WAS ORIGINALLY AUTHORED @
// VSCode appendix (TASKS) - "https://code.visualstudio.com/docs/editor/tasks-appendix"
// NOTE: This is written in typescript, and hasn't been compiled (which is probably obvious to most). See below for a real world example:
interface RunOptions {
/** ----------------------------------------------------------------------
* Controls how variables are evaluated when a task is executed through
* the Rerun Last Task command.
* The default is `true`, meaning that variables will be re-evaluated when
* a task is rerun. When set to `false`, the resolved variable values from
* the previous run of the task will be used.
-------------------------------------------------------------------------- */
reevaluateOnRerun?: boolean;
/** ------------------------------------------------------------------------
* SPECIFIES WHEN A TASK WILL RUN:
*
* VALID VALUES ARE:
* "default": The task will only be run when executed through the Run Task command.
* "folderOpen": The task will be run when the containing folder is opened.
---------------------------------------------------------------------------*/
runOn?: string;
}
}
runOptions
is added as a base property to the task, a real life example looks like this:
// THIS EXAMPLE WAS ORIGINALLY AUTHORED @
// VSCode's v(1.30) Release Notes - "https://code.visualstudio.com/Docs/editor/tasks"
// FILENAME: .../.vscode/tasks.json
{
"type": "npm",
"script": "strict-null-check-watch",
"label": "TS - Strict Null Checks",
"isBackground": true,
"problemMatcher": {
"base": "$tsc-watch",
"owner": "typescript-strict-null",
"applyTo": "allDocuments"
},
"runOptions": {
"runOn": "folderOpen"
}
}
Sources:
* Example 1) VSCode appendix (TASKS)
* Example 2) VSCode's v(1.30) Release Notes
So, I know this works in the Ubuntu Shell, and I would expect that it executes fine in Powershell. As I stated earlier, I use Linux 100%, and nothing else. If Powershell is a true shell, as its name suggest, then it will work...
In the command line type each command with a SEMI-COLON (;
) appended to the end each-one. You don't have to append a semi-colon to the last command. What the semi-colon does, is it tells the shell where the end of a command is at. When the shell reads the text after the semi-colon, it now knows that it is reading a new command, and it will continue to interpret that new command as a single separate command that ends at the next semi colon. The process continues recursively... you can enter 100 commands in one line this way.
~/$ cd client; npm start; cd server; npm run dev
You are trying to start a server, and a client in one go. I am guessing that they wont be able to both be able to use the same terminal to start, and run, their instances. If the terminal runs a program that doesn't end, like a server, the terminal wont be able to start another program until the server is done running, therefore you will need to open another terminal to run your client in.
Upvotes: 1