liveBook · Manning

Extension manifest

As explained in LLMs in Production

An extension manifest is a configuration document that declares an editor extension's identity, capabilities, activation behavior, and contributions.

An extension manifest is the configuration document that tells VS Code what an extension is, when to start it, which code to load, and how it changes the editor. In a generated project, it lives in package.json alongside extension.js. section 10.3

A practical manifest typically coordinates:

  • Runtime behavior through main and activationEvents; activation can be delayed until a relevant command or file event occurs, reducing unnecessary startup work. section 10.3

Coding-copilot manifest

A coding assistant can activate on editor.action.inlineSuggest.trigger, load ./extension.js, and contribute an Alt+S shortcut. This gives users deliberate control instead of sending requests whenever they stop typing.

How LLMs in Production covers it

How deep it goes
Explains manifest fields through a working example but stops short of detailing the full VS Code manifest schema.
Examples
Uses a coding-copilot manifest with manual inline-suggestion activation and an Alt+S keybinding.
What it assumes
Assumes familiarity with generated VS Code extension projects and package.json while explaining the manifest’s essential fields directly.
What you can do after
Configure a VS Code extension to activate on demand and expose commands or shortcuts through package.json.
How it connects
Connects package.json with activation events, commands, keybindings, extension.js, and inline completion providers.
Cover of LLMs in Production
liveBookmanning.com
Read LLMs in Production on liveBook Get the book at manning.com

This explainer was generated by Manning's knowledge graph from the text of LLMs in Production. The section links point to the parts of the book it draws on.