curated source
Sentry
Error monitoring, tracing and performance tooling.
What docspack can build from it
Sentry publishes an llms.txt index
but no llms-full.txt, so docspack build follows the index and fetches each linked page. Use --pages to
cap how many it retrieves.
$ npx docspack build sentry \ --name @sentry-docs/docspack \ --pkg-version 2026.1.0
That writes .llms/manifest.json, .llms/chunks/*.md
and an llms.txt table of contents — an ordinary npm package you can
publish to your registry or keep inside the monorepo that uses it.
Then an agent asks it
$ pnpm add -D @sentry-docs/docspack $ npx docspack sync $ npx docspack ask "monitoring"
The answer is scoped to the version in your lockfile, capped at 3,000 tokens, and read from a local SQLite index — no network request at query time.
Before you mirror someone else's docs
A mirror is a snapshot you own and version, not a live feed: it reflects
Sentry's documentation at the moment you ran build, and it
goes stale unless you rebuild. Pick a --pkg-version scheme that says
when it was taken rather than one that implies it tracks their releases. And their
documentation is their copyright — check the terms before publishing a mirror publicly;
a private package inside your own registry raises no such question.