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

persephone-audit-trail

v1.0.3

Published

persephone-audit-trail

Downloads

97

Readme

Installation

Always use the latest version of the package.

npm install [email protected]

Operation


Each update will create a history record with jsonDiff of the change. This helps in tracking all the changes happened to an object from the beginning.

Following will be the structure of the diff history being saved:

diff Collection schema:

_id : mongo id of the diff object
collectionName: Name of the collection for which diff is saved
collectionId : Mongo Id of the collection being modified
diff: diff object
user: User who modified
reason: Why the collection is modified
createdAt: When the collection is modified
_v: version

Usage


Use as you would any Mongoose plugin:

var mongoose = require('mongoose'),
    diffHistory = require('persephone-audit-trail'),
    schema = new mongoose.Schema({ ... });
    schema.plugin(diffHistory.plugin);

The plugin also has an omit option which accepts either a string or array. This will omit the given keys from history. Follows dot syntax for deeply nested values.

const mongoose = require("mongoose");
const diffHistory = require("persephone-audit-trail");

const schema = new mongoose.Schema({
  someField: String,
  ignoredField: String,
  some: {
    deepField: String
  }
});

schema.plugin(diffHistory.plugin, { omit: ["ignoredField", "some.deepField"] });

EXAMPLES

CREATE

const workflow = new Workflow({
      name,
      slug,
      description,
      priority,
      status,
      trigger,
      schedule,
      entity,
      end_chain,
      steps,
    });
    workflow.__user = "userID/ workflow"
     await workflow.save();

UPDATE

    createdWorkflow.name = 'rename';
    workflow.__user = "updaterID/ workflow"
    createdWorkflow = await createdWorkflow.save();

DELETE

    await Workflow.findByIdAndDelete( createdWorkflow._id,
        {__user: "deleterID/ workflow"},
    )