- This folder contains all of the files necessary for your web extension.
package.json* this is the manifest file in which you declare your extension and command.src/web/extension.ts* this is the main file for the browserwebpack.config.js* the webpack config file for the web main
- git clone https://github.com/Watts-Lab/deliberation-lab-tools.git
- cd deliberation-lab-tools
- Install Node.JS and VSCode
- Open the repository in a VSCode workspace
- Run
npm install. - Run
npm install -g vsceto install vsce CLI
- When working on a new feature, run
git checkout -b [your-feature-name]
- Uninstall the existing version of your extension:
- Run
vsce package - Install newly packaged extension in one of two ways:
- Restart VSCode and observe new functionality
- Test files are organized by functionality:
- src/test/suite/detection.test.ts – tests for detection logic
- src/test/suite/diagnostics.test.ts – tests for diagnostics
- src/test/suite/preview.test.ts – tests for preview behavior
- Test runner setup:
- All tests are executed via src/runExtensionTests.js, which invokes src/test/suite/index.ts.
- To run all tests:
- Run npm test
- Note: If this command fails, make sure you’ve run npm install first.
- To run specific test files:
- Use npm test --TEST_FILES {test_file_name} {test_file_name} ...
- Examples:
- npm test --TEST_FILES detection.test.js — runs detection tests only
- npm test --TEST_FILES diagnostics.test.js — runs diagnostics tests only
- npm test --TEST_FILES detection.test.js diagnostics.test.js — runs both in order
- Follow UX guidelines to create extensions that seamlessly integrate with VS Code's native interface and patterns.
- Check out the Web Extension Guide.
- Publish your extension on the VS Code extension marketplace.
- Automate builds by setting up Continuous Integration.



