[serhalp]

🔗 Linked issue

See #78, #2890. See also #2568.

🧭 Context

This implements the first part of the package collections feature as described in the ADR in #3421. (📘 Read the rendered ADR here.)

📚 Description

/collections/<handle>/<rkey> shows one collection: packages missing from the registry are struck through, included collections link to their own page, and anything unrecognized is shown so its author can fix it. The page notes that collections are the user's own public atproto data.

The editor orders items, adds packages through the package typeahead or by pasting a package or collection link, and takes an optional short note per item. It says up front that everything is public, and why a record from another app can't be saved yet. Saving an edit made stale by a change elsewhere fails with a conflict message instead of clobbering it.

Writes go to the signed-in user's PDS through their OAuth session, which now asks for the collections scope. Edits are read-modify-write with swapRecord, so a concurrent change fails with 409 instead of being clobbered. Fields other apps added are kept. Our own writes update the record cache, so the next read sees them right away; it would be confusing UX otherwise.

Also:

• Show your collections on your profile. When viewing your own profile, show a "Create new collection" CTA.
• Jump to your collections from the command palette.
• When viewing a package, add it to a collection from the command palette.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
npmx.dev	Ready	Preview	Nov 14, 2026 10:48pm UTC

2 Skipped Deployments

Project	Deployment	Actions	Updated
docs.npmx.dev	Ignored	Preview	Nov 14, 2026 10:48pm UTC
npmx-lunaria	Ignored		Nov 14, 2026 10:48pm UTC

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

Failed checks: 2 inconclusive

Check name	Status	Explanation	Resolution
Title check	(Error)	This assessment has not completed. The check will be retried on the next pre-merge check run.
Description check		This assessment has not completed. The check will be retried on the next pre-merge check run.

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the tracking.ignoredKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
i18n/locales/en.json	Source changed, localizations will be marked as outdated.
i18n/locales/fr-FR.json	Localization changed, will be marked as complete. 🔄️

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
3650	1	3649	6

View the top 1 failed test(s) by shortest run time

test/unit/a11y-component-coverage.spec.ts > a11y component test coverage > should have accessibility tests for all components (or be explicitly skipped)

Stack Traces | 0.0175s run time

AssertionError: Missing a11y tests for 1 component(s):
  - Collection/ItemNote.vue

To fix: Add tests in test/nuxt/a11y.spec.ts or add to SKIPPED_COMPONENTS in test/unit/a11y-component-coverage.spec.ts with justification.: expected 1 to equal +0

- Expected
+ Received

- 0
+ 1

 ❯ test/unit/a11y-component-coverage.spec.ts:186:12

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}