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

@echoppe/client

v0.3.0

Published

SDK client typé pour l'API Échoppe — généré depuis l'OpenAPI.

Downloads

720

Readme

@echoppe/client

SDK client typé pour l'API Échoppe — généré depuis le contrat OpenAPI de l'API. Runtime-agnostique (navigateur, Bun, Node, edge) : repose uniquement sur fetch.

Installation

bun add @echoppe/client

Utilisation

import { createEchoppeClient } from '@echoppe/client';

const echoppe = createEchoppeClient({
  baseUrl: 'https://api.maboutique.fr',
});

const { data, error } = await echoppe.GET('/products/');
if (error) throw error;

// `data` est entièrement typé depuis le contrat de l'API
for (const product of data) {
  console.log(product.name);
}

Les méthodes suivent le contrat OpenAPI via openapi-fetch : GET, POST, PUT, PATCH, DELETE, avec params.path, params.query et body typés par route.

const { data } = await echoppe.GET('/products/{id}', {
  params: { path: { id: '…' } },
});

Authentification

L'API utilise des cookies de session HTTP-only. Le client force credentials: 'include' — dans un navigateur, les cookies de session sont donc transmis automatiquement une fois l'utilisateur connecté via les routes d'auth.

Types

Le contrat complet est réexporté pour dériver ses propres types :

import type { paths, components } from '@echoppe/client';

type Product = components['schemas']['...'];

Régénérer depuis l'API

Le SDK est généré depuis l'OpenAPI d'une API en cours d'exécution :

# API sur http://localhost:7532 par défaut
bun run generate
# ou une autre instance
ECHOPPE_API_URL=https://api.exemple.fr bun run generate

Cela met à jour openapi.json (snapshot figé du contrat) puis src/openapi.ts.