@hint/hint-manifest-file-extension

Correct manifest extension (manifest-file-extension)

manifest-file-extension warns against using non-standard file extensions for the web app manifest file.

Why is this important?

While the .webmanifest file extension is not enforced by the specification, nor is it required by browsers, using it makes it:

• easier to set custom server configurations for the web app manifest file
• possible to benefit from existing configurations

What does the hint check?

The hint checks if the recommended .webmanifest file extension is used for the web app manifest file.

Examples that trigger the hint

<link rel="manifest" href="site.json">

<link rel="manifest" href="site.manifest">

Examples that pass the hint

<link rel="manifest" href="site.webmanifest">

How to use this hint?

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": {
        "manifest-file-extension": "error",
        ...
    },
    "parsers": [...],
    ...
}

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

Further Reading

• Web App Manifest Specification