Skip to content

fix: official vim/math/mermaid install and shared Dripnex userData - #567

Merged
tomymaritano merged 1 commit into
developfrom
cursor/official-plugin-install-b441
Aug 22, 2026
Merged

fix: official vim/math/mermaid install and shared Dripnex userData#567
tomymaritano merged 1 commit into
developfrom
cursor/official-plugin-install-b441

Conversation

@tomymaritano

@tomymaritano tomymaritano commented Aug 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

Packaged users can enable Vim (and mermaid/math) from Settings → Plugins without cloning a repo. Official slugs resolve to GitHub owner/repo, Browse keeps fallback cards when the live registry omits them, Updates match id or repository, and the CLI writes to the same Dripnex userData folder as the packaged app.

No marketplace. Official first-party packs only. AuthGate untouched.

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Related Issues

Closes #547
Closes #562

What changed

  1. Install specdripnex-vim-mode and dripnex/plugin-vim both resolve to dripnex/plugin-vim (same for mermaid/math). GET /plugins/:slug 404 no longer blocks Install. Decision: docs/plugins/install-path.md.
  2. Browse — already merged fallback catalog (docs: official first-party plugin research #563). This PR also lists mermaid/math in COMMUNITY_CATALOG so they stay visible if the API drops them.
  3. UpdatesmatchRemoteForInstalled matches scan().id to registry slug or the same GitHub repository (and the fallback catalog).
  4. userData (Vim Mode install is broken in packaged 0.16.0 (registry slug, not GitHub repo) #562 addendum)resolveUserDataRoot includes packaged productName Dripnex on Linux/Windows/macOS, prefers a root that already has dripnex.db / plugins/, and defaults to Dripnex so dripnex-plugin install lands in the folder the packaged app scans.

Checklist

  • I've read CONTRIBUTING.md
  • Targeted unit tests pass (storage-core data-paths, plugin-cli installSpec, desktop githubInstall + communityCatalog)
  • Typecheck: storage-core, plugin-cli, desktop main + renderer
  • Full pnpm test / pnpm build (not required for this path-only change)
  • PR targets develop branch (not main)

Test plan

  • Settings → Plugins → Browse still shows Vim when the registry lists it and when it is omitted (fallback merge)
  • Install dripnex-vim-mode and dripnex/plugin-vim both land dripnex-vim-mode-1.2.0.tar.gz in packaged userData plugins/
  • Updates lists vim when a newer registry/repo version exists
  • CLI and packaged app resolve the same userData root for productName Dripnex (Linux ~/.config/Dripnex, Windows %APPDATA%/Dripnex, macOS ~/Library/Application Support/Dripnex)
  • Unit tests: githubInstall, installSpec, communityCatalog, data-paths
  • No store UI, no clipper/graph/AI-notetaker, no dripnex/ios / Psynth / Linear PSY
Open in Web Open in Cursor 

Official slugs (dripnex-vim-mode, mermaid, math) resolve to their
GitHub owner/repo so Settings and dripnex-plugin do not 404 on a
missing registry row. Updates match scan id or repository. CLI
userData prefers the packaged Dripnex productName path.

Closes #547 and #562.

Co-authored-by:  Tomás Maritano <tomymaritano@gmail.com>
@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@tomymaritano, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 57 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9013b7bc-bdc0-4c1a-90bd-91c45a44ca7f

📥 Commits

Reviewing files that changed from the base of the PR and between 6f266c2 and d35d5c2.

📒 Files selected for processing (14)
  • apps/desktop/src/main/plugins/__tests__/githubInstall.test.ts
  • apps/desktop/src/main/plugins/githubInstall.ts
  • apps/desktop/src/renderer/pages/settings/sections/plugins/BrowseTab.tsx
  • apps/desktop/src/renderer/pages/settings/sections/plugins/UpdatesTab.tsx
  • apps/desktop/src/renderer/pages/settings/sections/plugins/__tests__/communityCatalog.test.ts
  • apps/desktop/src/renderer/pages/settings/sections/plugins/communityCatalog.ts
  • docs/PLUGIN_SYSTEM.md
  • docs/plugins/README.md
  • docs/plugins/install-path.md
  • packages/plugin-cli/src/installSpec.ts
  • packages/plugin-cli/tests/installSpec.test.ts
  • packages/storage-core/src/data/DataPaths.ts
  • packages/storage-core/src/data/index.ts
  • packages/storage-core/tests/data-paths.test.ts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@tomymaritano
tomymaritano marked this pull request as ready for review August 22, 2026 17:54
@tomymaritano
tomymaritano merged commit 68ffe0f into develop Aug 22, 2026
19 checks passed
@tomymaritano
tomymaritano deleted the cursor/official-plugin-install-b441 branch August 22, 2026 18:01
tomymaritano added a commit that referenced this pull request Aug 22, 2026
Includes #567 Settings plugin install plus main's release-pipeline fixes (#537/#539/#540). Do not squash.
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 0.16.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

tomymaritano added a commit that referenced this pull request Aug 22, 2026
<!-- CURSOR_AGENT_PR_BODY_BEGIN -->
## Summary

Packaged Linux 0.16.1 still wrote plugins/DB/logs under
`~/.config/@dripnex/desktop` because Electron `app.getPath('userData')`
follows package.json `name` `@dripnex/desktop`. #567 only aligned CLI
`resolveUserDataRoot`. This PR sets the Electron app name and userData
to productName `Dripnex` before `createDataPaths`, so the packaged app
and `dripnex-plugin` share one folder.

## Type of Change

- [x] Bug fix
- [ ] New feature
- [ ] Breaking change
- [x] Documentation update

## Related Issues

Closes #572

## What changed

1. **Runtime** — `applyProductUserData()` runs before Sentry and
`requestSingleInstanceLock`. It calls `app.setName('Dripnex')` and
`app.setPath('userData', resolveUserDataRoot())` unless Chromium already
has `--user-data-dir` (e2e).
2. **Package metadata** — root `productName: "Dripnex"` plus
electron-builder `extraMetadata.productName` so packaged `package.json`
does not rely on the scoped npm name for `app.getName()`.
3. **No silent migrate** — existing `@dripnex/desktop` with `dripnex.db`
or `plugins/` stays put via `pickUserDataRoot`. Fresh installs use
`~/.config/Dripnex` / `%APPDATA%/Dripnex` / `~/Library/Application
Support/Dripnex`.
4. **Docs** —
[`docs/plugins/install-path.md`](docs/plugins/install-path.md) records
the packaged-app contract.

No marketplace. No iOS. No release cut.

## Checklist

- [x] I've read [CONTRIBUTING.md](../CONTRIBUTING.md)
- [x] Targeted tests pass (`@dripnex/storage-core` 29,
`@dripnex/plugin-cli` 19) and desktop/storage-core typecheck
- [ ] Full `pnpm test` / `pnpm build` (not required for this path-only
change)
- [x] PR targets `develop` branch (not `main`)

## Test plan

- [x] Unit: `resolveElectronUserData` names the app `Dripnex`, defaults
to the packaged folder on Linux/Windows/macOS, keeps an existing scoped
folder that already has `dripnex.db`, honors `DRIPNEX_DATA_DIR`, leaves
`--user-data-dir` alone
- [ ] Packaged Linux log `dataDir` is `~/.config/Dripnex` on a fresh
machine
- [ ] CLI `dripnex-plugin` and the packaged app resolve the same plugins
dir
- [ ] e2e `--user-data-dir` / `DRIPNEX_DATA_DIR` still isolate tests

<!-- CURSOR_AGENT_PR_BODY_END -->

<div><a
href="https://cursor.com/agents/bc-4d7bdc7f-21c2-43f5-9215-8ae46bc3b625?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-web-light.png"><img
alt="Open in Web" width="114" height="28"
src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a>&nbsp;<a
href="https://cursor.com/background-agent?bcId=bc-4d7bdc7f-21c2-43f5-9215-8ae46bc3b625&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source
media="(prefers-color-scheme: light)"
srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img
alt="Open in Cursor" width="131" height="28"
src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a>&nbsp;</div>



<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **New Features**
  * Rebranded the desktop app as Dripnex.
* Improved shared data-folder handling between the desktop app and CLI.
* Added support for explicitly configured custom user-data directories.
  * Preserved existing application data across supported configurations.

* **Documentation**
  * Updated installation guidance for user-data directory resolution.

* **Tests**
* Added coverage for platform-specific paths, custom directories, and
application naming.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Vim Mode install is broken in packaged 0.16.0 (registry slug, not GitHub repo) Now: Vim/math/mermaid install that actually works

2 participants