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 🙏

© 2024 – Pkg Stats / Ryan Hefner

aboss-events

v1.0.1

Published

Javascript client to fetch ABOSS events

Downloads

7

Readme

This package provides a small and simple client to fetch public events from the ABOSS API. ABOSS is a platform for artist, managers and booking agents.

Installation

To install, use one of the following commands:

npm install aboss-events
yarn add aboss-events
pnpm add aboss-events

Usage

Importing the Client

First, import the createClient function from the package:

import { createClient } from 'aboss-api-client';

Configuration

Create a client instance by providing the required configuration parameters:

const client = createClient({
  agencyId: 'your_agency_id', // Optional
  artistId: 'your_artist_id', // Required
  token: 'your_api_token',    // Required
});

Fetching Public Events

Fetch public events by calling the publicEvents method on the client instance. You can optionally pass a date range:

const allEvents = await client.publicEvents();

const eventsIn2024 = await client.publicEvents({
  from: new Date('2024-01-01'),
  to: new Date('2024-12-31'),
});

API Reference

createClient(config: AbossClientConfig): AbossEventsClient

Creates and returns an ABOSS API client. Reference the ABOSS API documentation for more information about finding your token. Please keep in mind that if the token is from an agency account, you must also provide the agency ID.

Parameters

  • config: An object containing the client configuration.
    • agencyId (optional): The ID of the agency.
    • artistId (required): The ID of the artist.
    • token (required): The API token for authentication.

AbossEventsClient.publicEvents(options?: PublicEventsOptions): Promise<AbossEvent[]>

Fetches public events for the configured artist. Note that both the from and to parameters should be provided if you want to filter events by date range. This is a limitation of the ABOSS API.

Parameters

  • options (optional): An object to specify the date range for events.
    • from: The start date for the event range (inclusive).
    • to: The end date for the event range (inclusive).

Returns

A promise that resolves to an array of events. The Event object is fully typed according to the ABOSS API documentation.

Contributing

Contributions, whether in the form of code enhancements, bug fixes, or documentation, are always welcome! Here are the steps to get started:

  1. Fork the project repository. This creates a copy of the project on your account that you can modify without affecting the original project.
  2. Clone the forked repository to your local machine using a Git client like Git or GitHub Desktop.
  3. Create a new branch with a descriptive name (e.g., new-feature-branch or bugfix-issue-123).
git checkout -b new-feature-branch
  1. Make changes to the project's codebase.
  2. Commit your changes to your local branch with a clear conventional commit message that explains the changes you've made.
git commit -m 'feat: Implemented new feature.'
  1. Push your changes to your forked repository on GitHub using the following command
git push origin new-feature-branch
  1. Create a new pull request to the original project repository. In the pull request, describe the changes you've made and why they are necessary. Make sure to update or add documentation and test as relevant. I will review your changes, provide feedback, or merge them into the main branch.

License

MIT © Wannes Salomé