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 🙏

© 2025 – Pkg Stats / Ryan Hefner

restql-client-next

v1.0.2

Published

A structured RestQL client adapter for Next.js Server Components.

Downloads

299

Readme

restql-client-next

A robust, type-safe client adapter for building complex RestQL queries in Next.js applications, optimized for Server Components and Server Actions.


🛠️ 2. Setup (Initializing the Client)

The restql-client-next package uses a factory pattern (createRestqlClient) which requires you to provide your specific API fetch logic. This is essential for handling authentication, base URLs, and error handling in your environment.

2.1. Define the Custom Fetch Function

This function wraps the native fetch API, adding necessary logic like setting the base URL, attaching authentication tokens, and handling detailed API errors.

// lib/api/services/api.ts (Example Fetch Wrapper)

'use server';

import { getAuthTokenServer } from '../auth/auth-helpers'; // Assuming an auth helper

const BASE_URL = process.env.ADMIN_API_URL || 'http://localhost:3000/api';

export async function fetchApi<T>(
    endpoint: string,
    options: RequestInit = {},
): Promise<T> {
    const url = `${BASE_URL}${endpoint}`;
    const token = await getAuthTokenServer();

    const headers: Record<string, string> = {
        ...(options.headers as Record<string, string>),
    };
    
    if (!(options.body instanceof FormData)) {
        headers['Content-Type'] = 'application/json';
    }
    if (token) {
        headers['Authorization'] = `Bearer ${token}`;
    }

    const response = await fetch(url, { ...options, headers });

    if (!response.ok) {
        // Detailed error handling...
        let errorDetail = `HTTP error! Status: ${response.status}`;
        try {
            const errorBody = await response.json();
            errorDetail = errorBody.message || errorDetail;
        } catch {
            errorDetail = response.statusText;
        }
        throw new Error(errorDetail);
    }

    if (response.status === 204) {
        return {} as T;
    }

    return response.json() as Promise<T>;
}

2.2. Instantiate the RestQL Client

Use the factory function to create a ready-to-use client instance and export a wrapper function for consumption in your application.

// lib/api/restql.ts

'use server';

import { createRestqlClient } from 'restql-client-next';
import { fetchApi } from './services/api';

// 1. Instantiate the client with your custom fetch function
const restqlClient = createRestqlClient(fetchApi);

/**
 * Public export function for consuming the RestQL client.
 * @param queryName The resource path (e.g., "collection", "users")
 * @param params The structured RestQL parameters
 */
export async function findWithRestQL<T = any>(queryName: string, params?: any): Promise<T> {
    return restqlClient.findWithRestql(queryName, params);
}

Usage example

The client accepts a structured object for fields, filters, and includes, which it automatically serializes into the correct RestQL query string before sending the request via fetchApi.

    const collections: ICollection[] = await findWithRestQL("collection", {
        fields: [
            {field: 'id'},
            {field: 'name'},
            {field: 'goal'},
            {field: 'description'},
            {field: 'image'},
            {field: 'status', filters: [{ op: "==", type: "string", value: { OR: ["Completed", "Active"]}}]}
        ],
        includes: [
            {relation: "collected", fields: [
                {field: "totalUah"}
            ]},
            {relation: "category", fields: [
                {field: "name"},
                {field: "color"}
            ]}
        ]
    })