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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@isomerpages/isomerpages-travisci-scripts

v1.4.10

Published

A set of scripts that facilitates the production and deployment of Isomer pages

Readme

Isomer TravisCI Scripts

This package contains a set of scripts that facilitates the production and deployment of Isomer pages using TravisCI.

Specifically, it checks for syntax errors in the Markdown and YAML files used by Isomer, and sends details of the errors to a designated Slack channel using a webhook. On commit or merge to the master branch (i.e. to production), it also waits for the Netlify build process to complete and purges the KeyCDN cache to ensure that all visitors will receive the latest copy of the site.

Isomer Integration

First, install this package as a dependency:

npm install @isomerpages/isomerpages-travisci-scripts

Follow Slack's instructions for creating an app with a webhook for the channel you want the script to send error messages to. Add this webhook address to your TravisCI environment as the SLACK_URI environmental variable. Add the SLACK_ALERT_URI, KEYCDN_API_KEY, KEYCDN_ZONE_ID, NETLIFY_SITE_ID, NETLIFY_ACCESS_TOKEN, STAGING_URL, and PROD_URL environmental variables as well.

Make sure all secret key environmental variables are hidden!

Create the file .travis.yml in the root directory of your site's repository:

#.travis.yml
language: node_js
node_js:
  - "node"
git:
  depth: 3
script: node travis-script.js
cache: npm

Create the file travis-script.js in the root directory of your site's repository:

//travis-script.js
const travisScript = require("@isomerpages/isomerpages-travisci-scripts");
const travisBranch = process.env.TRAVIS_BRANCH;

if(travisBranch == "master") {
    travisScript.runAll();
}
else {
    travisScript.testsOnly();
}

Feel free to customise travis-script.js as you please. See below for a more complete documentation of the methods in the package.

This is all you need to get started! Give yourself a pat on the back, sit back, and let Slack handle the rest!

Methods

runAll

runAll() is a method that optionally takes in the boolean parameter sendSlack, which defaults to true if left unspecified.

If sendSlack is set to false, the error output will not be sent to Slack. However, you can continue to see the output generated in the TravisCI build log.

runAll() will run the Isomer syntax checker, the CDN purger, and the Lighthouse scan for the production site. It should be run when commits/merges are made in the master branch.

It does not return any value - all output is sent to standard output and Slack (if enabled, and does not include any CDN purging errors).

testsOnly

testsOnly() is a method that optionally takes in the boolean parameter sendSlack, which defaults to true if left unspecified.

If sendSlack is set to false, the error output will not be sent to Slack. However, you can continue to see the output generated in the TravisCI build log.

As its name implies, testsOnly() will only run the Isomer syntax checker and the Lighthouse scan for the staging site. It should be run for commits on staging branches.

Running testsOnly(false) is also a great way to preview the error output locally to fix any preexisting issues before deploying it on a site's repository. You don't want to suddenly send a barrage of error messages to the user's Slack channel!

It does not return any value - all output is sent to standard output and Slack (if enabled).

purgeCacheOnly

purgeCacheOnly() is a method that optionally takes in the boolean parameter sendSlack, which defaults to true if left unspecified. It only runs the CDN cache purger, skipping the Isomer syntax checker.

It does not return any value. Errors during execution, if any, are sent to standard output only. However, if the Netlify build timeouts (i.e. build is not successful after 10 minutes), an alert will be sent to Slack if sendSlack is true.