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

@hint/parser-manifest

v2.3.20

Published

webhint parser for web app manifest files

Downloads

74,889

Readme

Manifest (@hint/parser-manifest)

The manifest parser detects if a web app manifest file was specified, and if so, it will try to fetch it, parse and check if its content is valid.

This package is installed automatically by webhint:

npm install hint --save-dev

To use it, activate it via the .hintrc configuration file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        ...
    },
    "parsers": ["manifest"],
    ...
}

Note: The recommended way of running webhint is as a devDependency of your project.

Events emitted

The following events are emitted by the parser:

fetch::start::manifest

Event is of type FetchStart and is emitted when the parser starts downloading the web app manifest file.

fetch::end::manifest

Event is of type FetchEnd and is emitted when the parser successfully downloaded the web app manifest file.

fetch::error::manifest

Event is of type FetchError and is emitted when the parser encounters a problem trying to fetch the web app manifest file.

parse::end::manifest

Event is emitted when the parser successfully completed parsing the web app manifest file.

Format:

export type ManifestParsed = FetchEnd & {
    /** The content of manifest parsed */
    parsedContent: Manifest;
};

parse::error::manifest::json

Event is emitted when the content of the web app manifest file is not valid JSON.

Format:

export type ManifestInvalidJSON = ErrorEvent & {
    /** The parse JSON error. */
    error: Error;
};

parse::error::manifest::schema

Event is emitted when the content of the web app manifest file is not valid according to the schema.

Format:

export type ManifestInvalidSchema = ErrorEvent & {
    /** The parse errors as returned by ajv. */
    errors: ajv.ErrorObject[];
    /** The errors in a more human readable format. */
    prettifiedErrors: string[];
};

Types

If you need to import any type or enum defined in this parser, you just need to import them as follows:

import { TypeOrEnumYouWantToUse } from '@hint/parser-manifest';