vscode-extension-packaging

Community

Ship VS Code extensions across targets.

Authorcc01cc
Version1.0.0
Installs0

System Documentation

What problem does it solve?

Developers often struggle to package VS Code extensions for multiple runtimes (ESM/CJS), WASM assets, and platform-specific release targets, leading to inconsistent builds and manual toil.

Core Features & Use Cases

  • Supports dual-entry packaging for desktop and web extensions, with separate build outputs.
  • Provides guidance for bundlers (esbuild/webpack), WASM asset handling, and VSIX packaging.
  • Applies to CI workflows that validate build, package, and smoke tests across platforms.

Quick Start

Build a packaging plan that targets both desktop and web runtimes for a VS Code extension, including ESBuild/CJS-ESM interop and WASM asset handling.

Dependency Matrix

Required Modules

None required

Components

references

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: vscode-extension-packaging
Download link: https://github.com/cc01cc/cmtx-project/archive/main.zip#vscode-extension-packaging

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.