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

codeartifact-login

v2.0.0

Published

log into AWS CodeArtifact without AWS CLI

Downloads

329

Readme

codeartifact-login

CircleCI Coverage Status semantic-release Commitizen friendly npm version

Log into AWS CodeArtifact, without using AWS CLI

Provides a Node.js API, and a CLI wrapper. Both will set the registry and auth token in your npm config.

If you omit the domain and repository options, codeartifact-login will try to determine them from the current registry in your npm config if it's a CodeArtifact repository endpoint, and update the auth token. Otherwise the domain and repository options are required.

If you provide the namespace option, codeartifact-login will configure npm to use the registry for that package scope (similar to npm login --scope).

Node.js API

export default async function codeartifactLogin(options: {
  /**
   * Configuration for creating a default CodeartifcatClient
   */
  awsConfig?: CodeartifactClientConfig
  /**
   * CodeartifactClient to use
   */
  codeartifact?: CodeartifactClient
  /**
   * Codeartifact domain
   */
  domain?: string
  /**
   * Codeartifact domain owner (AWS Account ID)
   */
  domainOwner?: string
  /**
   * Codeartifact repository
   */
  repository?: string
  /**
   * Duration of auth token, in seconds
   */
  durationSeconds?: number
  /**
   * Codeartifact package namespace (npm package scope)
   */
  namespace?: string
  /**
   * Working directory to run `npm config` commands in
   */
  cwd?: string
  /**
   * `npm config` location to use
   */
  location?: 'global' | 'user' | 'project'
}): Promise<{
  /**
   * Codeartifact auth token
   */
  authorizationToken: string
  /**
   * Codeartifact reposiory endpoint
   */
  repositoryEndpoint: string
}>

CLI

codeartifact-login

log into CodeArtifact

Options:
  --version          Show version number                               [boolean]
  --help             Show help                                         [boolean]
  --region           AWS region                                         [string]
  --domain           CodeArtifact domain                                [string]
  --domainOwner      AWS Account ID                                     [string]
  --repository       CodeArtifact repository                            [string]
  --durationSeconds  auth token duration, in seconds                    [number]
  --namespace        package scope                                      [string]
  --location         npm config location                                [string]