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

code-challenge-seo-linter

v1.0.4

Published

A SEO linter package for users scan HTML file and show all of the SEO defects.

Downloads

10

Readme

This is a practicing npm package. Please do not use this package in production.

Installation

npm i --save code-challenge-seo-linter

Usage

const SeoLinter = require('../index.js');

const seoLinterInstance = new SeoLinter({
  "customizeRulesFolder": [__dirname + "/helps"],
  "runStartsWithOnly": [],
  "inputTarget": "test/index.html",
  "outputTarget": ""
});

seoLinterInstance.exec();

Description

  • You can test your HTML with the inputTarget parameter, or pass a readable stream to exec() method.

    // ...
    const Readable = require('stream').Readable;
    const rs = new Readable;
    rs.push('<!DOCTYPE html>');
    rs.push('</html>');
    rs.push(null);
    
    seoLinterInstance.exec(rs);

  • Put your customize seo rules in the customizeRulesFolder, and start with '08' (01~07 are used for basic rules). And filename should follow '08_{description}.js' this pattern. Your customize javascript rules should follow the response format :

    module.exports = function (dom) {
      return {
        hasError: () => true,
        output: `you got error`
      };
    };
  • If you don't want to run all the rules, put the rule sequence into the runStartsWithOnly array. For example : "runStartsWithOnly": ["01", "08", "03"].

  • Keep outputTarget empty and get the response thru console, or give it a writeable file path.