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

npfe

v0.2.0

Published

New Project From Existing git-repo

Downloads

1

Readme

New Project From Existing

Clones a git-source to a specific directory and replaces all source-name occurencies by a name of the new Project.

Installation

# sometimes, sudo prefix is required
npm i -g npfe

.

Usage examples

npfe memorizes a URI specified before and makes it possible to use aliases for source projects.

npfe new-project https://github.com/klimcode/base-cra cra

## later
npfe new-project-2 cra

If called w/o arguments then the config file will be opened.

npfe

If source URI or Alias is not specified then the first memorized alias will be used

npfe new-project

.

CLI

npfe <new-project-name> <URI | alias> <new-alias>

npfe considers if <URI | alias> contains a dot symbol (.) then it's a URI else it's an alias.

If URI specified and it is not memorized yet then the <new-alias> argument will be used as an alias for the URI specified. If <new-alias> is not spesicied then a placeholder source_# will be used as an alias.

.

Configuration

  1. sources -- is a list of source repos
  2. firstForced -- if true then npfe will silently use the first source repo for cases where <URI | alias> is omitted.
  3. clearHistory -- if true then the commits history will be cleared.
  4. gitUriTemplate -- is a URI for the new project's git origin. %repo% will be replaced by the new project's name automatically.
  5. commands -- a list of terminal commands that will be executed at the final stage. It's convenient to place a npm install command here, e.g.

package.json

All occurrences of the source project's name will be replaced by the new project's name in the package.json file.