local-extension-development

You can build and debug Neon Pilot extensions locally by packaging a self-contained folder with extension.json, optional src/, and dist/ bundles. This allows iterative in-app testing and reloading via the Extension Manager without needing a full source checkout.

The iterative reload workflow lets you inspect installed extensions, snapshot, edit, build, validate, and reload changes directly in-app using the Extension Manager. This streamlines the testing loop for bundled extensions during local development.

Yes, local extension development requires knowledge of the extension.json structure, the Extension Manager workflow, and how to run builds outside the app using provided tooling to properly validate and load bundled extensions.

The best way to validate native extensions before publishing is to use the Extension Manager to ensure proper loading and surface exposures. This safe testing process confirms the dist/ bundles function correctly within the Neon Pilot app.

Extension changes may not load if the dist/ bundles are not built correctly or the extension.json structure is invalid. You must use the provided tooling to build outside the app and then use the Extension Manager to validate and reload the extensions.

Yes, you can test bundled extensions without source checkouts by creating a self-contained extension folder. This includes the extension.json file and the compiled dist/ bundles necessary for the Extension Manager to load and validate the extension in-app.