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 🙏

© 2026 – Pkg Stats / Ryan Hefner

git-clone-to-new-repo

v1.0.2

Published

Clone Git repo to new one with no connections to the original

Readme

npm-package

Clone Git repo to new one

Clone Git repo to new one with no connections to the original

The new repo will have an empty history and no remotes, everything else will be as in the original. Note that only the default branch (if more than one exists) will be cloned.

hh lohmann <[email protected]>

Synopsis

  import { gitCloneToNewRepo } from 'git-clone-to-new-repo'

  gitCloneToNewRepo( urlOfRepoToClone, nameForNewRepo )

  gitCloneToNewRepo( urlOfRepoToClone, nameForNewRepo, branchName )

Parameters

urlOfRepoToClone

URL of the repo to clone

nameForNewRepo

Name / path for repo to create

branchName

Optional: Name for branch with which new repo is created

  • Default: 'main'

Returns

  • true on success, false else

Examples

  gitCloneToNewRepo(
    'https://github.com/acme-com/solve-all-problems',
    'my-super-solver'
  )

  gitCloneToNewRepo(
    'https://github.com/acme-com/postpone-hard-problems',
    '/home/joedoe/backlog/hard-problems'
  )

  gitCloneToNewRepo(
    'https://github.com/acme-com/soft-problems',
    'my-guaranteed-solver',
    'dev-branch'
  )

Installation

Pick for your preferred package manager:

  npm i git-clone-to-new-repo
  pnpm i git-clone-to-new-repo
  bun i git-clone-to-new-repo
  # For Yarn you should double check docs for your and / or
  # current Yarn version, newer versions do not treat `i package_name`
  # as an alias for `add ...` and exclude global installations
  yarn add git-clone-to-new-repo

Details

  • The new repo will be initialized, but without any commit. This allows you to further refine the new repo by deleting or changing files copied from the original repo in advance.

  • Unlike degit not meant for automation, therefore far simpler and sometimes faster

  • Cloning is done with "--depth 1" to clone only the current state. Note that this may only have for large repos an effect on the size of what is downloaded since in very small repos the Git tracking may consume more space than the tracked files. Note also that the actual size of the new repo will be that after deleting the former Git tracking.

Source Code

License