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

@ampproject/toolbox-validator-rules

v2.10.1

Published

A library that helps query AMP Validator rules

Downloads

141,317

Readme

AMP-Toolbox Validator Rules

npm version

Queries published AMP Validator rules and extracts information about required markup and attributes for all AMP formats.

Usage

Install via:

$ npm install @ampproject/toolbox-validator-rules

Including the Module

ES Module (Browser)

import validatorRules from '@ampproject/toolbox-validator-rules';

CommonJs (Node)

const validatorRules = require('@ampproject/toolbox-validator-rules');

Using the module

  // Loads the validator rules remotely with default options
  const rules = await validatorRules.fetch();


  // The raw unprocessed rules
  console.log(rules.raw);

  // All tags, combined with their respective attribute lists
  console.log(rules.tags);

  // All extensions
  console.log(rules.extensions);

  // Get all tag names used in AMP for Email
  // The supported formats are AMP, AMP4EMAIL, AMP4ADS and ACTIONS
  const tags = rules.getTagsForFormat('AMP4EMAIL');

  // Display their names
  console.log(tags.map(tag => tag.tagName));

  // Get information about an extension
  const ext = rules.getExtension('AMP4EMAIL', 'amp-carousel');

  // Display supported versions
  console.log(ext.versions);

Format of rules

The rules used closely follow the proto definitions from validator.proto.

Specifically:

  • The raw property is unprocessed ValidatorRules, the same format used by https://cdn.ampproject.org/v0/validator.json
  • The result of getTagsForFormat and the tags property is a list of TagSpec
  • The result of getExtension is ExtensionSpec with the htmlFormat field from TagSpec
  • The extensions property a list of ExtensionSpec with the htmlFormat field from TagSpec
  • The errors property combines ErrorFormat and ErrorSpecificity

Options

fetch optionally accepts an options object allowing you to customize its behaviour.

The following options are supported:

  • noCache: true to always fetch latest rules (by default, subsequent calls to fetch reuse the same result).
  • rules: object to use locally specified rules instead of fetching them from the AMP CDN.
  • url: override the URL where validator rules are fetched from.
  • source: one of 'local' (load rules from local file named "validator.json"), 'remote' (fetch rules from CDN) or 'auto' which is the default (tries looking for the local file first, then tries to fetch from CDN).

Example:

validatorRules.fetch({
  noCache: true,
  source: 'remote'
});