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

aditya-travis-size-report

v1.1.1

Published

Compare files from one build to another

Downloads

7

Readme

Travis size report

Let Travis tell you what changed compared to the last successful build on a particular branch. This helps you catch unexpected file renames and size changes.

Installation

npm install -D travis-size-report

Then, in .travis.yml:

after_success: sizereport --config

Config

Config file

This is typically sizereport.config.js.

module.exports = {
  repo: 'GoogleChromeLabs/travis-size-report',
  path: 'dist/**/*',
  branch: 'master',
  findRenamed: '[name]-[hash][extname]',
};
  • repo (required) - The username/repo-name.
  • path (required) - The glob (or array of globs) of files to include in the report.
  • branch (optional, default: 'master') - The branch to check against.
  • findRenamed (optional) - See below

findRenamed

By default, a renamed file will look like one file deleted and another created. However, you can help travis-size-report identify this as a renamed file.

findRenamed can be a string, or a callback. The string form can have the following placeholders:

  • [name] - Any character (.+ in Regex).
  • [hash] - A typical version hash ([a-f0-9]+ in Regex).
  • [extname] - The extension of the file (\.\w+ in Regex).

If you provide '[name]-[hash][extname]' as the value to findRenamed, it will consider foo-a349fb.js and foo-cd6ef2.js to be the same file, renamed.

The callback form is (oldPath, newPaths) => matchingNewPath.

  • oldPath - A path that existed in the previous build, but doesn't exist in the new build.
  • newPaths - Paths that appear in the new build, but didn't appear in the previous build.

Match up oldPath to one of the newPaths by returning the matching newPath. Or return undefined if oldPath was deleted rather than renamed.

Command line

sizereport [flags] repo path

Flags:

  • --config (or -c) - Path to the config file. If no path is provided, ./sizereport.config.js is the default.
  • --branch - Same as branch in the config file.

repo and path are the same as their equivalents in the config file.

It's recommended to use the config file rather than use args. If both are used, the command line args take priority over values in the config file.

Results

Results appear at the end of your Travis log. They're folded away by default, so you'll need to click on the sizereport line to expand it.