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

@bernankez/git-sync

v0.1.3

Published

Auto sync repos when pushing to git

Downloads

5

Readme

git-sync

npm CI LICENSE

Auto sync repos when pushing to git.

Install

git-sync should be installed in your project instead of globally.

$ npm i -D @bernankez/git-sync

Usage

  1. Create a config file named gitsync.config.ts or gitsync.config.js in the root of your project. For example

gitsync.config.ts

import { defineConfig } from "@bernankez/git-sync";

export default defineConfig({
  remoteName: "origin",
  url: ["[email protected]:Bernankez/git-sync.git", "[email protected]:Bernankez/example.git"]
});
  1. Run the CLI to update git config
$ npx git-sync
  1. You can also add the CLI to your package.json, so it can automatically run after npm install
{
  "scripts": {
    "prepare": "git-sync"
  }
}

[!NOTE] If you accidentally set the wrong git url and it has been added to your git, please go to the [project root dir]/.git and remove the line url = [your incorrect git url] in the config file.

Configuration

CLI

--config <path>

Specific where you want to read the config file from.

--git <path>

Specific git base dir.

Configuration file

remoteName

Remote name, defaults to origin.

fetch

If remoteName is not added, fetch will be used as the parameter when adding remote.

url

Git urls that you want to push to.

gitBaseDir

Same as --git in CLI. --git has higher priority than gitBaseDir.

What's behind

git init
git remote add <config.remoteName> <config.fetch>
git remote set-url --add <config.remoteName> <config.url>
git remote -v

License

MIT License © 科科Cole