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

@caucolum/api-query-object

v1.0.29

Published

Api-query-object is a JavaScript library that quickly and automatically creates HTTP requests, aligning with the client-server architecture.

Readme

Next Client Architecture

Api-query-object is a JavaScript library that quickly and automatically creates HTTP requests, aligning with the client-server architecture.

Features

With Api-query-object, the user can list their endpoints, automatically generating:

  • caucolumServer object: A class object whose methods are used on the server side, such as in getServerSideProps and getStaticProps.
  • caucolumClient object: A class object with the same methods as server, but with embedded business logic, for use on pages and components. These objects include:
    • makeRequest: A usable function to trigger the client request.
    • data: The response of the request.
    • args: Parameters of the last request.
    • status: Represents the current state of the request.
      It can be one of the following values:
      • 'idle': No request has been made yet.
      • 'loading': A request is currently in progress.
      • 'loaded': The request was completed successfully.
      • 'error': The request failed due to an error.

Usage Example

1. Install library:

npm i @caucolum/api-query-object

2. Created files

The created folder api-query-objects contains files for managing API queries.

api.ts: This file stores a list of available API endpoints used in the project. factory.ts: This file is responsible for creating and returning objects that represent specific API query configurations.

📁 my-project
├── 📁 src 
    └── 📁 api-query-objects
        └── 📄 api.ts
        └── 📄 factory.ts

3. Define Endpoints

In api.ts, user can implements him api endpoints:

import { ApiEndpoint } from "@caucolum/api-query-object";

const api = {

} as const satisfies Record<string, ApiEndpoint>;

export default api;

The objects are automatically created when implementing the user api endpoints:

import { createServerNextArchitecture, createClientNextArchitecture } from "@caucolum/api-query-object";
import api from "./api";

const caucolumServer = createServerNextArchitecture(api);
const caucolumClient = createClientNextArchitecture(caucolumServer, api);

export {
    caucolumServer,
    caucolumClient
}

Now just include your own API in api.ts:

import { ApiEndpoint } from "@caucolum/api-query-object";

interface BreedsImageRandomArgProps {
    breed?: string;
}

interface BreedsImageRandomDataProps {
    message: string;
    status: string;
}

interface BreedsHoudImagesDataProps {
    message: string[];
    status: string;
}

const api = {
    breeds_image_random: {
        url: '/breeds/image/random',
        method: 'get',
        authenticated: false,
        ARGS_PROPS: {} as BreedsImageRandomArgProps,
        DATA_PROPS: {} as BreedsImageRandomDataProps,
    },
    breed_hound_images: {
        url: '/breed/hound/images',
        method: 'get',
        authenticated: false,
        DATA_PROPS: {} as BreedsHoudImagesDataProps,
    },
} as const satisfies Record<string, ApiEndpoint>;

export default api;

4. Server-Side Usage (getServerSideProps)

import { caucolumServer } from "@/api-query-objects";

export const getServerSideProps = async () => {
    const response = await caucolumServer.breed_hound_images();
    return {
        props: {
            listByBreed: response.message
        },
    };
};

interface PageProps {
    listByBreed: string[];
}

const Index = ({ listByBreed }: PageProps) => {
    return <div>
        <div className="h-50 overflow-y-scroll">
            {listByBreed.map((breed, index) => (
                <div key={index}>{breed}</div>
            ))}
        </div>
    </div>
};

export default Index;

5. Client-Side Usage (React Component)

import { caucolumClient } from "@/api-query-objects";

const Index = () => {
    const { makeRequest, data, isSuccess } = caucolumClient.breeds_image_random();
    return <div>
        <div>
            {isSuccess && <img src={data.message} alt="" />}
            <button onClick={() => makeRequest()}>New request</button>
        </div>
    </div>
};

export default Index;