VSCE Template Registry

A public registry of scaffolding templates for building Deno-native 🦕 ⚡ VSCode Extensions with the vsce CLI.

---

Table of Contents

• Quick Start
• Template Manifest Schema
• Template Archive Requirements
• Adding a Template
• License

---

Quick Start

# Install (or update) the CLI
deno install -A -f -q -n vsce jsr:@vsce/cli@latest

# List all community templates
vsce templates list

# Scaffold a new extension from the "react-panel" template
vsce create my-extension --template react-panel

By default, the CLI fetches: https://raw.githubusercontent.com/cursor-ide/vsce-templates/refs/heads/main/index.yml.

You may override this via vsce.yml:

templates:
  registry: 'https://raw.githubusercontent.com/cursor-ide/vsce-templates/refs/heads/main/index.yml',
  cache: true,
  verifyHash: true,

---

Template Manifest Schema

The registry is a single YAML array; each element conforms to:

Field	Type	Required	Description
name	string	✔︎	Unique identifier used with --template <name>
description	string	✔︎	Short human-readable summary
url	string (URL)	✔︎	HTTPS link to a .zip or .tar.gz archive of the template
version	string (semver)	✖︎	Latest released version of the template
tags	string[]	✖︎	Search/filter keywords (e.g. ["react","webview"])
author	string	✖︎	Template maintainer(s)
license	string	✖︎	SPDX license identifier
homepage	string (URL)	✖︎	Project URL or documentation
sha256	string	✖︎	SHA-256 checksum of the archive (integrity verification)

Tip: Use YAML schema validation tools to verify your entries before opening a PR.

---

Template Archive Requirements

1. Root directory — When unpacked, the archive must contain a single top-level folder (same as name).
2. No pre-installed dependencies — Keep node_modules / dist out.
3. README.md explaining the template's features & instructions.
4. License — Each template must include a recognized open-source license file.

Optional niceties:

• .vscode/launch.json and tasks.json for a smoother dev experience.
• GitHub Actions or Deno workflows for CI testing the template itself.

---

Adding a Template

1. Fork this repo and create a new branch.
2. Upload your template archive to a permanent location (GitHub Release asset, S3, etc.).
3. Append a new object to index.yml following the schema above.
4. Commit + push; ensure CI passes (lint & schema validation).
5. Open a Pull Request – please include:
   • Link to source code
   • Screenshots or GIF demo (if UI-focused)
   • Any speciality permissions (deno.json), runtime requirements, etc.

Maintainers will review and merge once checks succeed.
Your template becomes instantly available to the community!

---

License

The registry index (index.yml) is licensed under the MIT License.
Individual templates are licensed as stated in their own repositories.

---

Made with ❤️ for Deno + VSCode! 🦕⚡ by Cursor IDE.