---
name: bijection-reactions-vllnt
description: "Evaluate and integrate the Reactions Vllnt component with Bijection."
---

# Reactions Vllnt

Reactions, votes, and likes on any resource — toggle, count by kind, and list reactors as a Bijection component

- Package: @bijectionhq/reactions-vllnt
- Category: Collaboration
- Status: Reference
- License: MIT
- Bijection source (repository access required): https://github.com/bijectionhq/reactions-vllnt/tree/58449db25af70c0524b9aad109f8e47727f42668
- Upstream: https://github.com/vllnt/convex-reactions/tree/0d319c156730d2939db55bfe00fc117509e1b52a
- Documentation: https://docs.bijection.com/components/using
- Directory: https://bijection.com/components/reactions-vllnt

## Get the source

Bijection repository access is required. Request access at https://bijection.com/contact.

```sh
git clone https://github.com/bijectionhq/reactions-vllnt.git
cd reactions-vllnt
git checkout 58449db25af70c0524b9aad109f8e47727f42668
```

## Before using this component

Read the package README at the recorded revision for setup, dependencies, and API examples. Upstream documentation describes the original package and may differ from the Bijection adaptation. This is a source candidate for evaluation. Catalog inclusion does not establish npm availability or runtime qualification. Check compatibility with your SDK and deployment before adoption. External providers run their own compute.

## Integration workflow

1. Read the source README and package manifest at the recorded revision.
2. Confirm the required SDK, dependency availability, and runtime compatibility.
3. Follow the component's documented setup and configuration. Never invent an npm install command from a catalog package name.
4. Keep credentials in the project's existing secret store.
5. Follow the project's execution rules for verification and report what was actually checked.

## Original upstream skill

The following guidance describes @vllnt/convex-reactions. Its installation commands and APIs refer to the upstream package. Evaluate compatibility with the Bijection source separately.


> Agents: read this skill fully before writing code that uses Reactions. Follow the installation and configuration steps exactly.

# Reactions

## Instructions

@vllnt/convex-reactions records a subject’s reaction to an opaque resource reference. Define a fixed reaction vocabulary or allow your own kinds, then read counts and the current subject’s state through Convex queries.

react toggles one author/resource/kind edge. unreact removes it idempotently. counts returns totals by kind; hasReacted and myReactions support active button states; reactors paginates the subjects behind a reaction. Multiple mounts keep separate systems isolated.

Your host resolves identity, authorizes access, and decides whether reaction types may coexist. A toggle is not a safe blind retry: use explicit removal or host idempotency when needed. Moderation, anti-abuse rules, ranking, and UI remain application concerns.

Maintained by [bntvllnt](https://bntvllnt.com) at [VLLNT](https://vllnt.com). Find the author on [GitHub](https://github.com/bntvllnt) and [X](https://x.com/bntvllnt).

### Installation

```bash
npm install @vllnt/convex-reactions
```

Current npm version: `@vllnt/convex-reactions@0.1.0`

## Use cases

- Communities: add likes or emoji reactions to posts and comments.
- Learning apps: collect helpful or unclear feedback on lessons.
- Games: let players react to shared results or community creations.
- Product feedback: attach votes to suggestions or feedback items.

## How it works

react toggles one author/resource/kind edge. unreact removes it idempotently. counts returns totals by kind; hasReacted and myReactions support active button states; reactors paginates the subjects behind a reaction. Multiple mounts keep separate systems isolated.

Your host resolves identity, authorizes access, and decides whether reaction types may coexist. A toggle is not a safe blind retry: use explicit removal or host idempotency when needed. Moderation, anti-abuse rules, ranking, and UI remain application concerns.

## When NOT to use

- When a simpler built-in solution exists for your specific use case
- If you are not using Convex as your backend
- When the functionality provided by Reactions is not needed

## Resources

- [npm package](https://www.npmjs.com/package/%40vllnt%2Fconvex-reactions)
- [GitHub repository](https://github.com/vllnt/convex-reactions)
- [Live demo](https://vllnt.com/)
- [Convex Components Directory](https://www.convex.dev/components/vllnt/convex-reactions)
- [Convex documentation](https://docs.convex.dev)