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

ods-diff

v1.1.3

Published

Highlight the diff between two LibreOffice spreadsheet

Downloads

5

Readme

node-ods-diff GitHub license GitHub tag

Highlight the diff between two LibreOffice spreadsheets with the simple node and CLI interfaces of ods-diff

NPM version JavaScript Style Guide Semver 2.0

Build Status Coverage Status

build status coverage report

CLI

Installation

$ npm install --global ods-diff

Usage

Output version

$ odsdiff -V
0.1.0

Output usage help

$ odsdiff -h

  Usage: odsdiff [options]

  Options:

    -h, --help                    output usage information
    -V, --version                 output the version number
    -v, --verbose                 output all intermediate steps informations
    -o, --f1 <path>               path of the original file to diff from
    -m, --f2, <path>              path of the modified file to diff to
    -O, --out [<path>]            destination path for the .ods diff output file
    -d, --csv-delimiter [<char>]  change the character delimiter for the CSV intermediate files

Standard usage:

$ odsdiff --f1 ./docs/v1/report.ods --f2 ./docs/v2/report.ods --out ./docs/report.diff.ods

Node API

Installation

$ npm install --save ods-diff

Usage

const odsDiff = require('ods-diff')
const path = require('path')

const reportv1Path = path.resolve('./docs/v1/report.ods')
const reportv2Path = path.resolve('./docs/v2/report.ods')
const reportDiffPath = path.resolve('./docs/report.diff.ods')

const odsDiffOptions = {
  cvsDelimiter: ','     // default: ';'
  verbose: true,        // default: false
  out: reportDiffPath   // default patern: './<f1_basepath>/<f1_basename>__diff__<f2_basename>.ods'
}


odsDiff(reportv1Path, reportv2Path, odsDiffOptions)
.then(() => console.log('ODS diff file successfuly written: ' + reportDiffPath))
.catch(err => console.error(err))

Note

Please note what name you must use depending what you are going to do with ods-diff

The repository name is node-ods-diff to show it is a node.js module

$ git clone https://github.com/sirap-group/node-ods-diff

The package name is ods-diff because we are in node.js context

$ npm i -s ods-diff
const odsDiff = require('ods-diff')

The CLI command is odsdiff, because it is more standard as a *nix CLI tool and it is quicker to tape on keyboard.

$ npm i -g ods-diff
$ odsdiff -v
1.1.0

Contributing

Pull Requests are welcome !

The code of the Node.js API is in index.js, and the code for the CLI API is located in bin/cli.js.

The code respects the standard js code style, please follow it too.

Standard - JavaScript Style Guide

Please note the following list of goals to achieve before starting to contribute.

TODO:

  • refactor index.js replacing most of the functions by prototypes and methods
  • write unit tests
  • setup gulp build with
    • js lint (standard)
    • run tests
    • run test coverage
    • watch changes then lint, test and coverage

License

MIT © Rémi Becheras, Groupe SIRAP