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

evolv

v0.1.5

Published

Apply new versions of your project instance

Downloads

2

Readme

Evolv

Apply new versions of your project instance

Follow the project

Installation

With npm:

npm install evolv

How to use

Introduction

Evolv is used to apply nodejs scripts updates in your project. When you deploy in a production server you have to apply database modifications, change folders structure, etc. Evolv executes version by version script to update your server instance to the last production version.

Apply versions

Require and use Evolv in your project:

var evolv = require('evolv');

evolv({}, '0.0.0', function(actualVersion, newVersion) {
  // callback
});

The first parameter lets you set options:

  • path (default: './version'): Set the path where your tasks are stacked.
  • silent (default: false): If you don't want to see all console.log from Evolv

The second parameter lets you start the script from a predefined version. By default it re-apply all versions.

The third parameter is the callback function. It gives you the predefined version given at first and the most recent version applied by Evolv.

Create version tasks

In your versions directory, you have to make one folder by MAJOR.MINOR version. On the inside, you have to create a version-MAJOR.MINOR.PATCH.js file with your task.

E.g.:

+-- version
    +-- 0.1
        +-- version-0.1.0.js
        +-- version-0.1.1.js
    +-- 0.2
        +-- version-0.2.10-my-feature.js

A task file works like a true NodeJS module. It's required like any other module but passing arguments:

'use strict';

module.exports = function(actualVersion, fileVersion, done) {

  // Do your evolve job here then call done()

  done();
};
  • actualVersion: The predefined version sent at first.
  • fileVersion: The version of the actual task file.
  • done: The callback function to call at the end.

Contribute

To contribute to the project, read the Contribution guidelines. After that, you can create your own Pull Requests (PR) and submit them here.

Lead contribution team