Recently, I made a helpful change by modifying the JavaScript of a VSCode extension that was installed in .vscode/extensions.
Following this, I decided to fork and clone the git repo with the intention of creating a pull request. To my surprise, I discovered that the JavaScript file I had modified was actually generated from TypeScript. Despite the code being somewhat similar, I replicated the changes. Now, I am eager to test this revised extension before submitting a pull request.
I attempted to transfer the altered repo contents to .vscode/extensions, and it appeared on the list of installed extensions. However, no matter how many times I reloaded, disabled, or re-enabled the extension within vscode, the JavaScript did not generate as expected.
While ensuring that tsc was properly installed and added to my PATH, I realized that these actions didn't seem to have any impact. No out directory was created, and no messages were displayed in the debug console -- indicating that there was no compilation process for the TypeScript taking place at all.
The available documentation only offers guidance on developing a new extension rather than troubleshooting an existing one that has been customized. Any suggestions or tips would be highly valued.
(These issues persisted on a Debian Linux system.)