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

s2r-package-npm

v1.0.1

Published

API client for API

Downloads

3

Readme

s2r-package-npm

API client

📋 API Information

  • API Title: API
  • API Version: 1.0.0
  • Generated: 2025-09-01

🚀 Installation

npm install s2r-package-npm

📖 Usage

Basic Usage

import { ApiClient } from 's2r-package-npm';

// Create client instance
const client = new ApiClient({
  baseURL: 'https://api.example.com',
  timeout: 10000
});

// Use API methods
try {
  const response = await client.someApiMethod(params);
  console.log(response.data);
} catch (error) {
  console.error('API Error:', error);
}

Configuration

import { ApiClient } from 's2r-package-npm';

const client = new ApiClient({
  baseURL: 'https://api.example.com',
  timeout: 10000,
  headers: {
    'Authorization': 'Bearer your-token'
  }
});

Error Handling

import { ApiClient, ApiError } from 's2r-package-npm';

try {
  const response = await client.someApiMethod(params);
} catch (error) {
  if (error instanceof ApiError) {
    console.error('API Error:', error.message);
    console.error('Status:', error.status);
    console.error('Response:', error.response);
  } else {
    console.error('Network Error:', error);
  }
}

🔧 Development

Build

npm run build

Watch Mode

npm run build:watch

Regenerate API Client

npm run generate

Start Mock Server

npm run mock

Validate API Document

npm run validate

📁 Project Structure

s2r-package-npm/
├── src/                 # Generated API client code
│   ├── api.ts          # API methods
│   ├── types.ts        # TypeScript types
│   ├── client.ts       # HTTP client
│   └── index.ts        # Main exports
├── dist/               # Compiled JavaScript
├── .s2r.json          # S2R configuration
├── tsconfig.json      # TypeScript configuration
├── package.json       # Package configuration
└── README.md          # This file

🔄 Updating the Client

When the API changes, you can regenerate the client:

# Update the swagger source in .s2r.json if needed
# Then regenerate
npm run generate
npm run build

📝 Configuration

The project uses .s2r.json for configuration. Key settings:

  • swagger.source: API document URL or file path
  • generation.outputDir: Where to generate code (default: ./src)
  • generation.excludeFiles: Files to preserve during regeneration

For more configuration options, see the S2R documentation.

🤝 Contributing

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🔗 Links


Generated with S2R - Swagger to Request