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

fed-config

v0.2.2

Published

## Contents

Downloads

2

Readme

fed-config

Contents

Why

This repo is intended to shorten the amount of effort needed to create multiple configuration files.

Prerequisites

You will need npx to run the scripts in this repository. This comes prepackaged with npm as standard from npm version 5.2.0. If you are using an early version of npm you can run npm i -g npx.

You'll also need to have already setup github ssh.

How to execute

Scripts in this repo are supposed to be quite easy to execute with no auth or other setup beyond what you will need for pushing/pulling/cloning.

The general pattern for executing scripts is

npx -p ClearScore/fed-config <script name>

Scripts

.npmrc script

When the script is executed it will ask for your email, full name, jFrog username, and jFrog password. Upon entering this information, a file called .npmrc will be created in your home directory and populated with the correct contents. If the file already exists an error message will be displayed, and the file will have to be deleted to use this script.

npx -p ClearScore/fed-config npmrc

.npmsyncrc script

This scripts needs to find the location of your npm-components folder, it will first check whether it has been executed in that folder. If it has not it will then traverse the directory tree, breadth-first, starting from your home directory. Therefore in order for this script to run as quickly as possible, execute it in your npm-components directory.

npx -p ClearScore/fed-config npmsyncrc

Yarn v2+ (Berry)

Do not run this within a project, but instead one level higher i.e. Run this within the 'dev' root for all projects

npx -p ClearScore/fed-config berry

Development

Executing branches

npx -p ClearScore/fed-config#<branch name> <script name>

Documentation

If you add any additional scripts please add an explanation of how to execute them and what they expect and do under the "Scripts" section.