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

syncb

v1.0.6

Published

A simple script to sync current branch with remote branch (Sync fork functionality)

Downloads

11

Readme

Syncb

Sync your forks using one command.

Blog: How I sync my forked repo with the parent using this CLI tool (saves me a lot of time)

syncb

Installation

Install syncb globally using npm:

npm i -g syncb
syncb

Description

syncb streamlines the process of synchronizing your local Git branch with the parent repository (upstream) from which you forked. It executes the following steps seamlessly:

  • Intelligent Upstream Detection: syncb intelligently determines the remote URL of the upstream repository based on common naming conventions used in Git forking workflows. This ensures it targets the correct source.
  • Automatic Upstream Setup (if needed): If no upstream remote is configured, syncb retrieves the parent repository's URL from the GitHub API. However, to access private repositories, you'll need to provide a valid GITHUB_TOKEN environment variable.
  • Seamless Change Fetching: syncb fetches the latest commits and code changes from the upstream repository, keeping your local branch in sync with the parent's evolution.
  • Careful Merge Integration: syncb integrates the fetched changes into your current local branch using a merge operation. This incorporates the upstream's updates while preserving your local modifications.

Using Private Forks

To use syncb with private forks, you'll need to create a personal access token on GitHub and set it as the GITHUB_TOKEN environment variable. Here's how:

  • Go to your GitHub settings (https://github.com/settings/tokens).
  • Click "Generate new token.", Use classic.
  • Give your token a descriptive name (e.g., "syncb-token").
  • Select the scopes needed by syncb: repo: Allows read access to private repositories.
  • Click on "Generate token."
  • Copy the generated token. This is your GITHUB_TOKEN.

Store it in your .zshrc or similar.

Important: Security: Do not share your personal access token publicly. Store it securely using environment variable managers or other secure methods.

Contributing

We're enthusiastic about contributions! If you have ideas to enhance syncb, feel free to submit an issue or pull request on the project's GitHub repository.

License

syncb is distributed under the MIT License (refer to the LICENSE file for details).