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

conflicts

v1.1.2

Published

Detects when a new file is different than an existing file and prompts the user for action.

Downloads

110

Readme

conflicts NPM version NPM monthly downloads NPM total downloads Linux Build Status

Detects when a new file is different than an existing file and prompts the user for action.

Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your :heart: and support.

Install

Install with npm:

$ npm install --save conflicts

Usage

const Conflicts = require('conflicts');
const conflicts = new Conflicts();

API

Conflicts

Create an instance of Conflicts with the given options and optional Vinyl constructor.

Params

  • options {Object}
  • File {Function}: Optionally pass a vinyl contructor, otherwise the default File class is used.
  • returns {Conflicts}: Returns an instance of Conflicts.

Example

const Conflicts = require('conflicts');
const conflicts = new Conflicts({}, require('vinyl'));

.detectFile

Compares an existing (old) file to a new proposed file, then prompts for an action if the files are not equal. If the contents of both files is identical, no action is taken, otherwise you will be prompted to choose the action to take. See the unit tests for examples of how to skip prompts.

Params

  • proposedFile {Object}: New file.
  • existingFile {Object}: Existing file.
  • options {Object}
  • returns {Promise}: Returns a promise with the action that was taken.

Example

conflicts.detect(fileA, fileB)
  .then(action => console.log('Action taken:', action))
  .catch(console.error)

.detectFile

Same as .detect, except the second argument is a string to an existing file on the file system.

Params

  • proposed {Object}: New file.
  • existingPath {Object}: File path to existing file.
  • options {Object}
  • returns {Promise}: Returns a promise with the action that was taken.

Example

conflicts.detectFile(file, 'path/to/file.txt')
  .then(action => console.log('Action taken:', action))
  .catch(console.error)

.files

Runs detect on an array of "proposed" files.

Params

  • files {Array}: Array of file objects.
  • options {Object}
  • returns {Array}

Example

conflicts.files([fileA, fileB, fileC])
  .then(action => console.log('Action taken:', action))
  .catch(console.error)

.diffFiles

Takes an array of "proposed" files, and returns an array of strings, where each string represents a diff of the proposed file's contents versus an existing file's contents.

Params

  • files {Array}
  • options {Object}
  • returns {Array}

Example

conflicts.diffFiles([fileA, fileB, fileC])
  .then(diffs => {
    diffs.forEach(diff => console.log(diff));
  })
  .catch(console.error)

.isEqual

Returns true if an fileA (existing/old) file appears to be identical to a fileB (proposed/new) file.

Params

  • proposed {Object}: vinyl file representing a proposed (new) file
  • existing {Object}: vinyl file representing an existing (old) file
  • options {Object}
  • returns {Boolean}

Example

console.log(conflicts.isEqual(fileA, fileB));

About

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.

Please read the contributing guide for advice on opening issues, pull requests, and coding standards.

Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:

$ npm install && npm test

(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)

To generate the readme, run the following command:

$ npm install -g verbose/verb#dev verb-generate-readme && verb

Author

Jon Schlinkert

License

Copyright © 2018, Jon Schlinkert. Released under the MIT License.


This file was generated by verb-generate-readme, v0.8.0, on December 08, 2018.