Events

Events lets you publish events and sell tickets to them. Signed-in users pick a ticket on the event page, pay through Stripe Checkout and show a QR code at the door. Staff set up the events, ticket types, add-ons and capacity in the admin area. Use it when your app sells or registers places at dated events. For recurring memberships, use Subscriptions instead.

The package is @frigear-nu/events. Money goes through Payments.

What you get

• Pages (opt-in): the event list at /events, an event page at /events/:slug, and the signed-in user's tickets at /account/tickets.
• Admin area (opt-in, with Admin): an event list at /admin/events, and an event page with Details, Tickets and Attendees tabs. With Widget, upcoming events also appear on the admin dashboard.
• Server routes (on by default): browsing events, buying and paying for tickets, and a staff API for events, attendees, refunds and check-in. The staff API is guarded by the events:manage and events:refundpermissions, which the admin role holds.
• Composables and helpers (on by default): useEvents, useEvent and useMyTickets.
• Emails. None built in. Send a confirmation from the events:ticket:paid hook, which runs when a ticket is paid.
• MCP tools (opt-in): browse events and tickets, and manage events as staff, through MCP.

Quick setup

pnpm add @frigear-nu/events @nuxthub/core

export default defineNuxtConfig({
  modules: ['@nuxthub/core', '@frigear-nu/events'],
  events: {
    settings: {
      pages: { events: true, event: true, tickets: true },
      reservationMinutes: 30,
    },
  },
})

pnpm db:generate

export default defineNuxtConfig({
  events: { settings: { roles: true } }, // ships the `eventmanager` role
  authorization: {
    roles: {
      // Roles are built from permissions. `events:*` covers events:manage and events:refund, but not events:pii.
      organiser: { label: 'Organiser', grant: ['events:*', 'events:pii'], inherit: ['user'] },
    },
  },
})

Options

Options go under the events key.

settings.reservationMinutes is also the lifetime of the Stripe Checkout session.

settings.pages.* paths keep the parameters of the default, such as :slug.

settings.roles. Registers the eventmanager role with events:manage, events:refund and events:pii, and also puts those three into admin. Without it, only admin holds them, unless your app grants them to a role of its own. Your own authorization.roles.eventmanager merges into the module's role: your label wins, and grant and inherit are added together.

Permissions

Events registers these permissions with Authorization. A staff route calls authorize(event, 'events:manage'); self-service routes call authorize(event, 'tickets:write').

• Scope: tickets (label "Your tickets") expands to tickets:read and tickets:write. A token or OAuth client with it can read and buy the user's own tickets, and is refused every staff route.
• Roles: eventmanager, shipped only with settings.roles: true.
• Requirements and policies: none. The module registers no requirement and no policy of its own. Add one with definePolicy when, say, an organiser may only edit their own events.
• Why events:refund is separate: money moves, so it is session only, and a token can never refund. A role that grants events:manage by name must grant events:refund too (events:* covers both).

See roles and requirements for how roles are built and merged.

Module pages

Next steps

• Sell event tickets – build the whole flow, from a new event to a paid ticket.
• Stripe setup – create the keys and the webhook that mark tickets as paid.
• Server API – limit tickets to members, or connect your own membership list.