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

folder-semver

v0.0.1

Published

Predict semver update type based on changes between 2 folders

Downloads

1

Readme

folder-semver Build Status

Compare two folders of assets and get a semver update type based on the differences in the files.

Use this module to keep track of changes in assets that are refered to by file name.

We treat the file names as the "method signatures", so for an asset that is changed but has the same name the change is a patch, whenver we add a file it is a minor and when a file is deleted or moved the change is a major.

How to use

folderSemver(oldFolderPath, newFolderPath, options)

Arguments:

  • oldFolderPath string
  • newFolderPath string
  • options object, can be used to activate verbose mode

The exported function returns:

  • null when there is no change in the files
  • "major" when the old build contains files not present in the new build. The api has changed and things depending of the old file structure might break.
  • "minor" when files are added to the new build. A new feature has been added to the api.
  • "patch" when the filenames are equal but there are other changes to the files. A bug has been fixed but the api is unchanged.

Example

var folderSemver = require('folder-semver')
folderSemver('oldBuild/assets', 'newBuild/assets');
// returns "major", "minor", "patch" or null

Example with verbose mode

Verbose mode will log a diff of the changes in the build to the console.

var folderSemver = require('folder-semver')
folderSemver('oldBuild/assets', 'newBuild/assets');
// + added_file.svg
// - removed_file.svg
// ~ changed_file.svg
// returns "major", "minor", "patch" or null

Tests

See tests.js for the test suite.

To run the test suite use this command.

npm test