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

gitlab-swagger-client-auth

v0.1.0-dev.2825740

Published

Helper for gitlab-swagger-client which requests and stores authentication details for GitLab

Downloads

16

Readme

gitlab-swagger-client-auth

Installation

npm install gitlab-swagger-client gitlab-swagger-client-auth -S

Configuration

// $HOME/.gitlab-swagger-client-authrc
{
  "gitlab": {
    "baseUrl": "https://gitlab.com/api/v3", // Defaults to https://gitlab.com/api/v3
    "token": "MY_API_TOKEN" // From https://gitlab.com/profile/account or https://gitlab.com/profile/personal_access_tokens
  }
}

The config file is loaded using rc, so config is merged from the following JSON/INI files (if they exist, in order of precedence):

  • Environment variables (e.g., $gitlab_swagger_client_auth_gitlab__baseUrl)
  • A .gitlab-swagger-client-authrc in the current directory (or the first found by navigating up the CWD path)
  • $HOME/.gitlab-swagger-client-authrc
  • $HOME/.gitlab-swagger-client-auth/config
  • $HOME/.config/gitlab-swagger-client-auth
  • $HOME/.config/gitlab-swagger-client-auth/config
  • /etc/gitlab-swagger-client-authrc
  • /etc/gitlab-swagger-client-auth/config

Usage

import { GroupsApi } from 'gitlab-swagger-client';
import createGitlabApi from 'gitlab-swagger-client-auth';

const groupsApi = createGitlabApi(GroupsApi);

Development

Integration tests

To run the integration tests, you will need to provide an access token for the gitlab.com API (obtained via the Web API). Run the following command to set the token in your NPM config:

npm config set gitlab-swagger-client-auth:gitlab-token TOKEN

Note, this is only used to make read requests against the gitlab-org group and doesn't access/modify any of your own data.