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

node-weblyse

v1.0.0-beta.3

Published

Analyse your website(s) with multiple tools.

Downloads

4

Readme

node.js Weblyse

A node.js library to analyse any website with multiple tools and get a report JSON.

Install

# npm
npm install node-weblyse

# yarn
yarn add node-weblyse

Usage

const weblyse = require('node-weblyse');

// the report file path is resolved using process.cwd()
// to enforce that it's relative to this file you can do
process.chdir(__dirname);

weblyse({
    urls: [
        // add as much URLs as you want
        // the report will contain all of them
        'https://github.com',
    ],
    // if you don't need a file just omit the reportFilePath key
    reportFilePath: './report.json', 
    // you con configure the single providers
    // enable/disable them via a simple boolean
    // or use an object for configuration values
    providers: {
        ssllabs: true,
        securityheaders: true,
        webhint: true,
        screenshots: true,
        lighthouse: true,
        axe: true,
    },
})
    .then(data => {
        // do whatever you want with the data Object
        // * assertions in your CI
        // * render a template
        // * post to monitoring service
        // ...
    })
    .finally(() => {
        // that's needed to end your node process
       process.exit(0);
    });

You can find an example report.json in the GitHub repository.