Skip to main content
A VS Code extension runs in the extension host, a Node.js process, so LanceDB’s TypeScript SDK (@lancedb/lancedb) runs inside it like any other npm package. There’s no database server to start: the extension opens a table on local disk and queries it in-process. That makes LanceDB a good fit for features such as semantic search over a workspace, retrieval for an AI assistant, or a cache of embeddings that survives restarts. The extension host differs from a plain Node.js script in three ways that trip people up:
  • Where you can write. Relative paths resolve against the extension host’s working directory, not the workspace, and that directory may be read-only.
  • Bundling. The default extension template bundles everything with esbuild, which can’t bundle LanceDB’s native .node binary.
  • Packaging. LanceDB installs a native binary for the current platform only, so a VSIX built on one OS doesn’t run on another.
This guide builds a small extension that handles all three. It indexes the Markdown files in a workspace and searches them by meaning, using a local embedding model, so no API key is needed.
What you’ll build
  • LanceDB: Index Markdown in Workspace splits every *.md file into paragraphs and stores them in a LanceDB table, with embeddings from Xenova/all-MiniLM-L6-v2 run locally through Transformers.js.
  • LanceDB: Search Markdown embeds your query, shows the five closest paragraphs, and opens the one you pick.

Create the extension

1

Scaffold a TypeScript extension

Use the official generator. Choose New Extension (TypeScript) and esbuild as the bundler.
2

Install LanceDB

Your code imports Arrow types directly, so add apache-arrow as a dependency, pinned inside LanceDB’s peer dependency range (>=15.0.0 <=18.1.0). If the project already depends on a newer apache-arrow, installing LanceDB fails with ERESOLVE.LanceDB also needs @types/node 22 or later. The generator’s template already uses a recent version; an old one causes Cannot find module 'node:stream' errors.You don’t need to install @huggingface/transformers yourself. LanceDB pins it as an optional dependency, and installing a different version gives your code a copy that LanceDB doesn’t use.
3

Skip type checking of dependencies

The type declarations of apache-arrow and the ONNX runtime used by Transformers.js refer to browser types such as ReadableStreamReadResult and HTMLCanvasElement. The template’s tsconfig.json doesn’t include the DOM library, so tsc reports errors inside node_modules. Turn on skipLibCheck:
tsconfig.json

Store the database in extension storage

Give LanceDB an absolute path inside the storage VS Code reserves for your extension:
  • context.storageUri: a folder for the current workspace. It’s undefined when no folder is open. Use it for anything derived from the workspace, such as this index.
  • context.globalStorageUri: a folder shared by all workspaces. Use it for things like downloaded models.
Neither folder is guaranteed to exist, so create it before connecting. Both live outside the user’s project, so the index never shows up in their files or in version control. Don’t pass a relative path such as lancedb.connect("data"). It resolves against the extension host’s working directory, which isn’t the workspace and may be read-only: this causes the Read-only file system (os error 30) error on macOS. Put the LanceDB code in its own module, src/search.ts:
src/search.ts
src/search.ts
Split each file into paragraphs, and keep the line each one starts on so a result can open the file at the right place:
src/search.ts
Create the table with LanceDB’s built-in huggingface embedding function. Because the text column is declared as the function’s source field, LanceDB computes the vector column for you as the rows are written:
src/search.ts
The table remembers its embedding function, so you can search it with plain text after VS Code restarts:
src/search.ts
mode: "overwrite" rebuilds the index each time, which is fine for a few thousand paragraphs. For larger workspaces, update only the files that changed with mergeInsert.

Wire up the commands

Declare the two commands in package.json:
package.json
Then register them in src/extension.ts:
src/extension.ts
A few details in this file are specific to running inside VS Code:
  • The index goes in storageUri, so each workspace gets its own table.
  • The embedding model (about 90 MB) downloads on first use. By default Transformers.js caches it inside node_modules in the installed extension, which is replaced on every update. Setting env.cacheDir keeps it in global storage. Load the module with import(), not require(): LanceDB loads the ES module build of @huggingface/transformers, and require() returns a separate copy whose settings LanceDB never sees.
  • Each paragraph is stored with its file’s URI, not a path relative to a workspace folder. In a multi-root workspace, findFiles searches every folder and two folders can hold the same relative path, so only the URI opens the right file. asRelativePath turns it back into a short label, which names the folder when there’s more than one.
  • When another extension or a test passes a query to lancedbSearch.search, it returns the rows instead of opening a picker. That’s how the results below were produced, with each URI shown through asRelativePath.

Sample results

Here are the results of running the extension in VS Code against a small workspace of six Markdown files that document a fictional CLI. The columns are the vector distance (lower is closer), the file and line, and the paragraph.
Neither top result shares a keyword with its query: “credentials were exposed” matches “a token leaks”, and “stuck behind the company firewall” matches “hangs … proxy”. Picking a result in the search box opens the file at that paragraph.

Bundle with esbuild

The template bundles your code and its dependencies into dist/extension.js. esbuild can’t bundle native binaries, so building with LanceDB fails with No loader is configured for ".node" files. Mark the packages that load native code as external so they’re loaded from node_modules at runtime:
External packages must be in the VSIX, but the template’s .vscodeignore excludes node_modules/**. Delete that line. vsce then includes your production dependencies and leaves out the dev dependencies. If you skip this step, the packaged extension fails to activate with Cannot find module '@lancedb/lancedb', and its commands report command 'lancedbSearch.index' not found.

Package a VSIX for each platform

npm installs LanceDB’s native binary only for the machine it runs on, such as @lancedb/lancedb-win32-x64-msvc on 64-bit Windows. Build one VSIX per platform, each on a matching machine or CI runner, and publish them all. The Marketplace serves each user the right one.
LanceDB doesn’t publish a binary for Intel Macs (darwin-x64). The table covers LanceDB’s own binaries. This sample’s local model also needs onnxruntime-node, which Transformers.js loads when the extension activates. Its Linux binaries link against glibc and it publishes no musl build, so the sample as written doesn’t run on Alpine, whatever --target you pass. To ship the alpine-* targets, embed with a hosted API or use full-text search instead, or build ONNX Runtime for musl yourself.
Native binaries make the VSIX large: the win32-x64 build of this extension is about 200 MB. onnxruntime-node, which Transformers.js uses, ships binaries for every platform. Excluding the ones a target doesn’t need brings the win32-x64 build to about 150 MB. Keep one ignore file per target and pass it with --ignoreFile:
.vscodeignore.win32-x64
If you don’t need a local model, embed text with a hosted API instead, or use full-text search, which needs no model at all.

Keep the extension host responsive

All extensions share one extension host, and loading the model and computing embeddings in it can stall the others. While the sample indexes, VS Code may briefly report that the extension host is unresponsive. That’s fine for a handful of files. For a large workspace, move indexing into a worker thread or a child process, and index in batches as files change instead of all at once.

Troubleshooting