vscode-extension-packaging

Packaging a VS Code extension for desktop and web targets requires dual-entry build outputs and separate VSIX configurations. This workflow provides concrete recommendations for bundlers, entry points, and asset copying to ensure consistent builds across runtimes.

Handling WASM assets when building VS Code extensions involves configuring specific asset copying rules and bundler settings. This packaging plan includes strategies for integrating WASM files into the final VSIX package without manual toil.

Resolving ESM and CJS interop issues during VS Code extension packaging requires configuring your bundler to handle dual module formats. This workflow provides concrete recommendations for esbuild and webpack to ensure compatible build outputs.

VS Code extension packaging supports CI validation for cross-platform releases by integrating build, package, and smoke test checks into your workflow. This approach validates VSIX outputs and platform-specific release targets automatically.

After running VSIX packaging for a VS Code extension, you should perform post-build checks to validate build outputs and WASM asset integrity. This workflow outlines specific post-build validation steps to ensure robust release targets.