@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?

To use it you will have to install it via npm:

npm install @hint/hint-manifest-file-extension

Note: You can make npm install it as a devDependency using the --save-dev parameter, or to install it globally, you can use the -g parameter. For other options see npm's documentation.

And then activate it via the .hintrc configuration file:

{
    "connector": {...},
    "formatters": [...],
    "hints": {
        "manifest-file-extension": "error",
        ...
    },
    "parsers": [...],
    ...
}

Further Reading

• Web App Manifest Specification