Skip to main content
You can test LynxHub extensions during development or after compiling them for production.

​
Development mode testing

LynxHub automatically boots your extension in development mode when the codebase exists in the project root.
  1. Place your extension project directory in the LynxHub repository root.
  2. Name the folder extension.
  3. Run the development server from the LynxHub root directory:
The application detects the /extension directory. It automatically loads your extension in development mode. The main process dynamically imports your code from extension/src/main/lynxExtension.ts. The renderer process imports your code from @lynx_extension/renderer/Extension.

​
Inspector and logs

You can inspect components and debug frontend behavior using the Electron developer tools.
  • Press Ctrl+Shift+I or F12 to open the developer tools.
  • You can inspect the DOM structure, verify styles, and run frontend console commands.
  • The main process prints backend logs directly to your terminal window.
  • Vite applies styling changes instantly using Hot Module Replacement (HMR).
  • You must restart the application if you modify backend files or entry point definitions.

​
Static validation

You should run validation scripts to check code quality and typescript compiler correctness. To test your extension code for errors, run the validation script in the LynxHub root directory:
This command executes the following tasks:
  • Formats your extension code using Prettier.
  • Checks your extension files for syntax and stylistic errors using ESLint.
  • Validates that your TypeScript files compile without type errors.

​
Production testing

You should test that your compiled extension loads correctly in production mode before distributing it.
  1. Build your extension for production.
  2. Manually copy the compiled files to your local Plugins directory.
  3. Launch LynxHub to verify that the extension initializes without errors.
  4. Read the Building extensions guide for detailed installation steps.
Last modified on June 18, 2026