Files
PaperClipAI/ui
683d7ae120 fix(ui): name the plugin whose UI module raised a browser error (#22487)
## Thinking Path

> - Paperclip is the open source app people use to manage AI agents for
work
> - The browser UI loads plugin UI modules. The host fetches each
module, rewrites its imports, and imports it from a random `blob:` URL
> - Browser errors go to Sentry. A stack frame from a plugin module
names only that random blob URL
> - So a Sentry report cannot tell which plugin raised an error. For
example, a plugin can abort its own request during an unmount, and the
report shows only `blob:https://<host>/<uuid>`
> - This pull request records each blob URL with its plugin key, and
tags the Sentry event with that plugin key
> - The benefit is that a plugin error can go to the correct plugin
owner, and the blob URL is never sent

## Linked Issues or Issue Description

Refs #22380, which marks the announcement card's own aborts as
intentional. Some events in the same Sentry group come from a plugin
module instead, and #22380 cannot cover them.

**What happened?**
Hosted browsers report `AbortError: signal is aborted without reason` as
an unhandled rejection. The innermost frame is a React effect cleanup in
a `blob:` module at line 5590. Only plugin UI modules run from `blob:`
URLs in the main thread. The event has no data that names the plugin.

**Expected behavior**
A Sentry event from a plugin module names the plugin, so the plugin
owner can fix the plugin.

**Steps to reproduce**
1. Install a plugin with a UI slot whose effect cleanup calls
`controller.abort()` on a pending `fetch` and does not catch the
rejection.
2. Open a page with that slot. Then go to a page without it.
3. Sentry records an unhandled `AbortError` whose frame is a `blob:` URL
and no plugin key.

## What Changed

- `ui/src/lib/plugin-module-origins.ts`: a new, bounded registry (100
recent modules). `rememberPluginModuleUrl` records a blob URL with its
plugin key. `readPluginModuleOrigin` finds the innermost `blob:` frame
of an event and returns its plugin key, `unmapped`, or nothing. It never
throws.
- `ui/src/plugins/slots.tsx`: `importPluginModule` records the blob URL
with the plugin key before the import.
- `ui/src/lib/sentry.ts`: `beforeSend` sets the `browser_plugin_module`
tag when an event has a `blob:` frame. The tag holds the plugin key (at
most 200 characters) or `unmapped`. It never holds the URL.
- Tests for the registry, the loader, and the Sentry hook.

## Verification

- `cd ui && npx vitest run src/lib/plugin-module-origins.test.ts
src/lib/sentry.test.ts src/plugins/slots-loading.test.tsx
src/plugins/slots.test.ts src/hooks/useAnnouncement.test.tsx`: 69/69
pass.
- Red first: with the source changes removed and the new tests kept, the
Sentry test and the loader test fail (`expected 'unmapped' to be
'fixture.navigation'`).
- `cd ui && npx vitest run src/lib src/plugins`: 279 files, 3231 tests
pass.
- `npx tsc --noEmit -p ui/tsconfig.json`: no errors in the changed
files.

## Risks

- Low risk. The change adds one tag. It does not drop, group, or change
any event.
- The tag holds a plugin key, which is a manifest identifier. It holds
no URL, path, or user data.
- The registry keeps at most 100 entries, so memory stays bounded when
modules reload.

## Model Used

- Claude Opus 5.5 (`claude-opus-5-5`), with tool use and code execution,
in Claude Code.

## Checklist

- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [ ] All Paperclip CI gates are green
- [ ] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [ ] I will address all Greptile and reviewer comments before
requesting merge

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: paperclipbugbot <356415228+paperclipbugbot@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-21 03:26:38 -08:00
..
…

@paperclipai/ui

Published static assets for the Paperclip board UI.

What gets published

The npm package contains the production build under dist/. It does not ship the UI source tree or workspace-only dependencies.

Storybook

Storybook config, stories, and fixtures live under ui/storybook/.

pnpm --filter @paperclipai/ui storybook
pnpm --filter @paperclipai/ui build-storybook

Typical use

Install the package, then serve or copy the built files from node_modules/@paperclipai/ui/dist.

Editor dependency identity

Keep the root and workspace overrides for @codemirror/state, @codemirror/view, and @lezer/common aligned. CodeMirror requires shared extension identity, while Lezer parsers and syntax highlighters require shared NodeProp IDs. Multiple Lezer copies can crash code-block highlighting with tags is not iterable. src/lib/codemirror-single-instance.test.ts checks the installed dependency graph and highlights sample code through the editor's real language dependencies. GitHub Actions owns regeneration of pnpm-lock.yaml.