bug: fixes spawning of watch-dev in VS Code

.vscode/launch.json

@@ -10,7 +10,7 @@
       "request": "launch",
       "args": ["--extensionDevelopmentPath=${workspaceFolder}"],
       "outFiles": ["${workspaceFolder}/dist/**/*.js"],
-      "preLaunchTask": "npm: compile-dev"
+      "preLaunchTask": "${defaultBuildTask}"
     },
     {
       "name": "Launch Tests",

.vscode/tasks.json

@@ -10,7 +10,20 @@
         "isDefault": true
       },
       "isBackground": true,
-      "problemMatcher": "$tsc-watch",
+      "presentation": {
+        "panel": "dedicated",
+        "reveal": "never"
+      },
+      "problemMatcher": [
+        {
+          "base": "$tsc-watch",
+          "background": {
+            "activeOnStart": true,
+            "beginsPattern": "asset .*",
+            "endsPattern": "webpack .* compiled .*"
+          }
+        }
+      ],
       "detail": "webpack --mode development --watch --progress"
     },
     {

CHANGELOG.md

@@ -12,6 +12,11 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 - Removes duplicate diagnostic messages from the linter
   ([#598](https://github.com/fortran-lang/vscode-fortran-support/issues/598))
 
+### Fixed
+
+- Fixed `npm run watch-dev` not syncing changes to spawned Extension Dev Host
+  ([#602](https://github.com/fortran-lang/vscode-fortran-support/issues/602))
+
 ## [3.2.0]
 
 ### Added

CONTRIBUTING.md

@@ -53,7 +53,7 @@ npm run compile-dev
 
 ### Developing & Debugging 🐞️
 
-You can now start writing code the `watcher` task will check for compilation errors.
+You can now start writing code, the `watcher` task, if not running, will automatically start when debugging.
 You can actively debug the extension by pressing <kbd>F5</kbd> with `Launch Extension` selected.
 
 👉 **Tip!** You don't need to stop and restart the development version of VS Code after each change. You can just execute `Reload Window` from the command palette in the