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

git-conflicts

v1.5.0

Published

Manual merge tool

Downloads

24

Readme

npm

git-conflicts

Build Status Coverage Status Dependency Status

Resolve merge conflicts in the editor. With conflicts, you do all the work yourself.

Usage

$ git conflicts

Searches for conflicts in unmerged files in the root Git directory and opens each one in the editor. You resolve one conflict, save and exit, and continue to the next.

Conflict resolution is a process of transforming this:

<<<<<<< branch1
Content from branch 1.
=======
Content from branch 2.
>>>>>>> branch2

into this:

<<<<<<< branch1
Resolved conflict.
>>>>>>> branch2

Note that conflicts assumes you leave header and footer lines and put resolved lines in between.

To skip a conflict, exit without resolution and select skip in the prompt.

$ git conflicts .

Similar to the no-arguments case, but searches for conflicts in the current directory as opposed to the root directory.

$ git conflicts [filename]...

Similar to the above, but each unmerged file name is additionally filtered to match one of the filenames specified in the arguments. Each filename must be a path to a file or a directory, relative to the current working directory.

Configuration

  • $EDITOR — set this variable to override the default editor.
  • $GIT_EDITOR — set this variable to override $EDITOR.

Install

npm install -g git-conflicts

License

MIT