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

configure-jfrog

v1.0.1

Published

Configure JFrog Artifactory for an NPM package.

Downloads

3

Readme

🐸 configure-jfrog 🐸

The command-line utility configure-jfrog is used to configure an NPM repository for using a JFrog SaaS Artifactory registry.

Installation

No installation is necessary when using npx, although you may globally install with npm install --global configure-jfrog. This is only recommended if you do not desire the latest version of the utility on each run.

Usage

Run the CLI command configure-jfrog with optional flags and answer any prompts that may appear.

configure-jfrog [--directory -d] [--server-name -n] [--artifactory-key -k] [--registry -r] [--scope -s]

⚠️ WARNING: configure-jfrog will replace any existing .npmrc file at the specified directory.

Flags

| name | alias | description | | ----------------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | directory | -d | The relative or absolute path to the directory in which to configure NPM. This should be the root directory where your package.json lives. | | server-name | -n | The JFrog Artifactory server name: https://__<server-name>__.jfrog.io | | artifactory-key | -k | Your Artifactory API key. You must generate one for your user profile. | | registry | -r | The name of the registry on Artifactory you would like to use. | | scope | -s | The NPM @scope that your private packages are published to. It is best practice to always publish private packages under a scope so that there are no conflicts with public packages of the same name. |

Example

npx configure-jfrog -d ~/Sites/example-package -n doximity -k $ARTIFACTORY_API_KEY -r npm-doximity -s dox

Run as npm script

It may be helpful to create an NPM script to automatically configure your repository for new users:

{
  "scripts": {
    "configure-npm":
      "npx configure-jfrog -d . -n doximity -k $ARTIFACTORY_API_KEY -r npm-doximity -s dox"
  }
}

This will allow a new user to set up the private registry using their credentials.