chore: use esbuild script for vscode tasks (denoland#597)

Author: jespertheend

.vscode/tasks.json

@@ -3,7 +3,7 @@
   "tasks": [
     {
       "type": "npm",
-      "script": "compile",
+      "script": "esbuild",
       "group": "build",
       "presentation": {
         "panel": "dedicated",
@@ -12,22 +12,6 @@
       "problemMatcher": [
         "$tsc"
       ]
-    },
-    {
-      "type": "npm",
-      "script": "watch",
-      "isBackground": true,
-      "group": {
-        "kind": "build",
-        "isDefault": true
-      },
-      "presentation": {
-        "panel": "dedicated",
-        "reveal": "never"
-      },
-      "problemMatcher": [
-        "$tsc-watch"
-      ]
     }
   ]
 }

README.md

@@ -153,8 +153,14 @@ steps:
 
 1. Open this folder in VS Code.
 2. Run `npm i`.
-3. Run `npm run compile`.
-4. Run the `Launch Client` launch task from the VSCode debug menu.
+3. Run the `Launch Client` launch task from the VSCode debug menu.
+
+After making changes to the extension you can use the restart button in the
+VSCode debug menu, this makes a new build and reloads the client.
+
+Note that if you already have the deno extension installed from the VSCode
+Marketplace, it will be replaced for the `Launch Client` instance only. So
+there's no need to uninstall your existing Deno extension.
 
 Most changes and feature enhancements do not require changes to the extension
 though, as most information comes from the Deno Language Server itself, which is

package.json

@@ -502,7 +502,6 @@
     "test-compile": "tsc -b",
     "fmt": "deno fmt .vscode .github client/src media typescript-deno-plugin/src typescript-deno-plugin/*.md docs package.json tsconfig.json README.md CHANGELOG.md",
     "lint": "deno lint --unstable client/src typescript-deno-plugin/src docs",
-    "watch": "tsc -b -w",
     "postinstall": "cd typescript-deno-plugin && npm i && cd ../client && npm i && cd .."
   },
   "dependencies": {