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

specht

v1.3.1

Published

Check links found in html or js files by pattern

Downloads

3

Readme

Specht

Dependency Status Current version Travis Build Status

Installation

$ npm install specht --save

Usage

CLI

$ specht --help

Usage: specht [path] [options]

Example: specht path/to/start/from \
--pattern https://www.jetbrains.com/hub/help/1.0/%s.html \
--ignore-file .gitignore \
--html-rules svg:xlink:href hub-page-help-link:url \
--js-rules getHelpUrlFilter getHelpUrlInSecondParameter:1 \
--html-extension .html .htm \
--teamcity

At least one of --js-rules or --html-rules parameters is required. Will exit
with code 1 otherwise.

Options:
  --pattern         Help site pattern, e.g.:
                    https://www.jetbrains.com/hub/help/1.0/%s.html. “%s”
                    placeholder is replaced with parts found by parsers
                                                                 [default: "%s"]
  --ignore-file     Files and directories to ignore, uses .gitgnore format.
                    Relative from path.
  --html-rules      Rules of parsing HTML files, in form of <tag
                    name>:<attribute name>. XML namespaces for attributes are
                    supported.                                           [array]
  --js-rules        Rules of parsing JavaScript files, in form of <function
                    name>[:<argument number, default is 0>].             [array]
  --html-extension  Extensions of HTML files        [array] [default: [".html"]]
  --js-extension    Extensions of JavaScript files    [array] [default: [".js"]]
  --teamcity        Report check results to TeamCity                   [boolean]
  --help            Show help                                          [boolean]

Programmatic

See fields descriptions above, however there are no defaults for programmatic usage

import createRunner from 'specht';

const runner = createRunner();

runner.start({
 rootDir,
 pattern,  
 ignoreFile,
 teamcity,
 htmlExtension,
 htmlRules,
 jsExtension,
 jsRules
});