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

@aligent/bigcommerce-api

v1.1.1

Published

Fully typed BigCommerce API client generated from documentation schemas

Readme

Aligent BigCommerce API Client

A JavaScript client for BigCommerce's Management API with full TypeScript typings for all API endpoints.

Features

  • Full coverage and Typescript typing for BigCommerce's Management REST APIs
  • Easy IDE autocompeletion of endpoints, parameters and response data
  • Automatic retry of intermittent errors such as 429 and 5xx with exponential backoff

Supported environments

  • Node.js >=18

Getting started

To get started with the JavaScript client you'll need to install it, and then follow the instructions for either the Storefront API client or the Management API client.

Installation

Node

npm install @aligent/bigcommerce-api

Notes on the source schemas

Management REST API schemas are taken from the BigCommerce documentation here: https://github.com/bigcommerce/docs/tree/main/reference

Undeclared REST methods

REST methods not declared in a schema are by default included in openapi-typescript with a value of never.

To improve UX and reduce complexity at compile time these methods are removed from the built types.

Accept and Content-Type headers

Almost all requests require a value of application/json for these headers - the exception being methods supporting multipart/form-data (e.g. image uploads).

For ease of use the exported client automatically sets the appropriate headers, and the required types are instead set to optional in the exported types.

"Empty" response codes

Some methods declare what appears to be an invalid or unnecessary additional response code with an empty object as the value for application/json.

These are removed from the generated Typescript types as they force users to check the response type when it should never be necessary (e.g. 201 on a GET request)

GET customers/{customerId}/metafields and customers/{customerId}/metafields/{metafieldId}

The response payloads for these are incorrectly declared in BigCommerce's documentation and schemas: https://github.com/bigcommerce/docs/issues/912

The generated types for these endpoints are currently incorrect as a result.

catalog/products/{product_id}/images and catalog/products/{product_id}/images/{imageId}

The documentation site pulls the schema for these endpoints from a different source.

Migration from @space48/bigcommerce-api

This library was built on the groundwork laid by the @space48/bigcommerce-api library (https://github.com/Space48/bigcommerce-api-js/).

BigCommerce have changed their published schemas substantially since the last time that library was built. If you are migrating, please check docs/CHANGED_PATHS.md.

[!WARNING]

There may be other changes to query, path, and response variables. Migration may require additional changes to your code.

Versioning

This project strictly follows Semantic Versioning.

New versions may include changes pulled from the BigCommerce source schemas. Look in docs/changelog for any resulting changes to interfaces.

Support

If you have a problem with this library, please file an issue here on GitHub.

Contributing

See CONTRIBUTING.md

License

MIT

Under development

  • [x] Easier customisation of fetch client
  • [ ] Expose the storefront API paths properly
  • [ ] Regular rebuild and publish schedule to keep up with BigCommerce API schema changes
  • [ ] Migrate generation code to Typescript
  • [x] Properly publish ESM and CJS exports
  • [ ] Audit eslint/typescript ignore comments
  • [ ] Audit type narrowing and parameter types (especially in v2)