npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@o2s/blocks.ticket-recent

v1.6.0

Published

A block displaying recent tickets and their comments.

Readme

@o2s/blocks.ticket-recent

A block displaying recent tickets and their comments.

The ticket-recent block shows a short list of the user's most recent tickets, configurable by limit (e.g. 3 or 5). It is typically used as a dashboard widget, letting customers quickly see their latest support activity and navigate to the full ticket list or details.

  • Recent tickets – Configurable limit (e.g. 3–5) from CMS
  • Quick access – Links to ticket details and full list
  • Dashboard widget – Compact view for dashboards
  • Auth-required – Scoped to logged-in user

Content editors set the limit and place the block. Developers connect a Tickets integration to power the data.

Domain

Domain: Support

Installation

npm install @o2s/blocks.ticket-recent

Usage

Backend (API Harmonization)

Register the block in app.module.ts:

import * as TicketRecent from '@o2s/blocks.ticket-recent/api-harmonization';
import { AppConfig } from './app.config';

@Module({
    imports: [
        TicketRecent.Module.register(AppConfig),
    ],
})
export class AppModule {}

Frontend

Register the block in renderBlocks.tsx:

import * as TicketRecent from '@o2s/blocks.ticket-recent/frontend';

export const renderBlocks = async (blocks: CMS.Model.Page.SlotBlock[]) => {
    return blocks.map((block) => {
        if (block.type === 'ticket-recent') {
            return (
                <TicketRecent.TicketRecentRenderer
                    key={block.id}
                    id={block.id}
                    slug={slug}
                    locale={locale}
                    accessToken={session?.accessToken}
                    userId={session?.user?.id}
                    routing={routing}
                />
            );
        }
        // ... other blocks
    });
};

SDK

Use the SDK to fetch recent tickets:

import { sdk } from '@o2s/blocks.ticket-recent/sdk';

// SDK uses NEXT_PUBLIC_API_URL for the API base URL
const recentTickets = await sdk.blocks.getTicketRecent(
    { id: 'block-id' },
    { 'x-locale': 'en' },
    accessToken
);

Configuration

This block requires the following integrations to be configured in AppConfig:

import { Tickets, CMS, Auth } from '@o2s/configs.integrations';

export const AppConfig: ApiConfig = {
    integrations: {
        tickets: Tickets.TicketsIntegrationConfig,  // Required
        cms: CMS.CmsIntegrationConfig,              // Required
        auth: Auth.AuthIntegrationConfig,            // Required
    },
};

Environment Variables

The required environment variables depend on which integrations you're using:

  • For Zendesk integration: See @o2s/integrations.zendesk documentation
  • For mocked integration: No additional environment variables needed

API

Block Endpoint

GET /api/blocks/ticket-recent/:id

Headers:

  • x-locale: Content locale (required)

Response:

{
    id: string;
    data: {
        tickets: Ticket[];
    };
}

Related Blocks

  • @o2s/blocks.ticket-list
  • @o2s/blocks.ticket-details
  • @o2s/blocks.ticket-summary

About Blocks in O2S

Blocks are self-contained, reusable UI components that combine harmonizing and frontend components into a single package. Each block is independently packaged as an NPM module and includes three primary parts: API Harmonization Module, Frontend Components, and SDK Methods. Blocks allow you to quickly add or remove functionality without impacting other components of the application.

About O2S

Part of Open Self Service (O2S) - an open-source framework for building composable customer self-service portals. O2S simplifies integration of multiple headless APIs into a scalable frontend, providing an API-agnostic architecture with a normalization layer.