vscode-tasks

How to make vscode not wait for finishing a preLaunchTask?

This worked for me. Note all these are required, even though none are important: problemMatcher.pattern.regexp problemMatcher.pattern.file problemMatcher.pattern.location problemMatcher.pattern.message problemMatcher.background.activeOnStart problemMatcher.background.beginsPattern problemMatcher.background.endsPattern { // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format “version”: “2.0.0”, “tasks”: [ { “label”: “build-extras”, “type”: “shell”, “isBackground”: true, “command”: “./script/build-extras”, // This task is run before some debug tasks. … Read more

Using a shell command as VSCode task variable value

This extension provides a way to launch arbitrary shell commands as a VS Code command: “tasks”: [ { “label”: “test_arch”, “type”: “shell”, “command”: “echo”, “args”: [ “${MYARCH}” ], “options”: { “env”: { “MYARCH”: “${input:get_arch}” } }, “problemMatcher”: [] }, ], “inputs”: [ { “id”: “get_arch”, “type”: “command”, “command”: “shellCommand.execute”, “args”: { “command”: “uname -m” } … Read more

vscode import error for python module

I tried to add this in my launch.json, then it works! “env”: {“PYTHONPATH”: “${workspaceRoot}”} below is my launch.json “name”: “Python: Current File (Integrated Terminal)”, “type”: “python”, “request”: “launch”, “program”: “${file}”, “cwd”: “${workspaceRoot}”, “env”: {“PYTHONPATH”: “${workspaceRoot}”}, “console”: “integratedTerminal” wish it can help u! 🙂

Define multiple tasks in VSCode

Just in case it helps someone… . If you don’t have/want gulp/grunt/etc… or an extra shell script to proxy out your task commands , “npm run” is there already . this is for webpack and mocha as in “Build and Test” , Shift+Ctrl+B, Shift+Ctrl+T .vscode/tasks.json: { “name”: “npmTask”, //… “suppressTaskName”: true, “command”: “npm”, “isShellCommand”: true, … Read more