This is a broader conversation of moving the file checking functionality into a separate module that can be configured in terms which files to run tests on, what kind of coverage logs to generate, etc. The language server would just import that module and send the results to the client to display. This separates the responsibilities of the vscode extension versus a coverage utility that could possibly be run in a continuous integration environment.

This module could include some of the following features:

Be run from a CLI
Generate coverage statistics
Be configurable for which files to include/exclude
Generate application/component timings in a synthetic environment

The README currently states that it is only supporting Angular. We support React now as well. The GIFs have the old visual experience and need to be updated.

As disccused with the team, there's benefit in moving the Mezzurite Tracking into a separate vs code tab. We can have the functionality for both and have this as a configuration setting.

Do we want some way of reporting user crash dumps? It looks like there's an existing package that assists with that, or we can find a different/custom solution.

The idea here is to have a step that uploads a .vsix extension as an artifact which can be consumed by a release pipeline.

Relevant documentation:
https://code.visualstudio.com/api/working-with-extensions/bundling-extension

As per the docs, reducing the number of files being loaded will improve the startup performance of the extension. As this extension is written using the language client/server protocol, it will need to be bundled into 2 different bundles: one for the client, and one for the server.

We can set up a release pipeline where we publish the built extension to the marketplace. We will need to consider all the different steps in the release script as well as the ability to hide the publisher authentication token as a secret.

Relevant documentation:
https://code.visualstudio.com/api/working-with-extensions/publishing-extension
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/variables?view=azure-devops&tabs=yaml%2Cbatch#secret-variables

This manifests itself in the form of 2 functions: isAngularjs and generateAngularjs.

For reference, here are the React implementations of isReact and generateReact.

Currently, the server starts up and crawls all the files in the directory and runs coverage on those files. Afterwards, the server listens for the client to send events using the vs code API to see if a file was deleted or changed. Chokidar is able to do this by just listening to the workspace and emitting events. This way, changes can be detected even when made by an external program, like git. This also eliminates the need for the client to request a recalculation to the server, as chokidar will be able to pick it up and send it to the client.

Related to #39, we can use chokidar to look inside package.json or node_modules to detect whether or not a the project has a Mezzurite dependency. This check would prevent the extension from doing the calculations on the workspace folders without a dependency on Mezzurite. Potentially, this could also hide the Mezzurite treeview or tab if it didn't exist.