Has web app manifest (`manifest-exists`)

manifest-exists warns when a [web app manifest][spec]
file is not provided.

Why is this important?

The web app manifest file constitutes a standard centralized place
to put metadata about your web application, and providing it:

* informs browsers (and possible [others][windows]) where to look
for information about your web app, information that they may need
in different contexts (e.g. what icon and name should be used if
your web app is added to the home screen)

* is an essential piece in the context of progressive web apps,
being one of the signals used by some browsers (e.g. [Chrome][chrome],
[Opera][opera], [Samsung Internet][samsung internet]) in deciding if
they will show the add to home screen prompt to users

What does the hint check?

This hint checks if:

* The web app manifest file is specified correctly in the page
(i.e. the page contains a single, valid declaration such as:
)

* The specified web app manifest file is accessible (i.e. requesting
it doesn’t result in a 404, 500, etc.)

$3

The web app manifest file is not specified:

``html example ... ...`

The location of the web app manifest file is not specified:

`html example ... ...`

More than one web app manifest file is specified:

`html example ... ...`

`$3`

`html example ... ...`

`How to use this hint?`

This package is installed automatically by webhint:

`bash npm install hint --save-dev`

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

`json { "connector": {...}, "formatters": [...], "hints": { "manifest-exists": "error", ... }, "parsers": [...], ... }`

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

Has web app manifest (`manifest-exists`)

manifest-exists warns when a [web app manifest][spec]
file is not provided.

Why is this important?

The web app manifest file constitutes a standard centralized place
to put metadata about your web application, and providing it:

What does the hint check?

This hint checks if:

* The web app manifest file is specified correctly in the page
(i.e. the page contains a single, valid declaration such as:
)

* The specified web app manifest file is accessible (i.e. requesting
it doesn’t result in a 404, 500, etc.)

$3

The web app manifest file is not specified:

``html example ... ...`

The location of the web app manifest file is not specified:

`html example ... ...`

More than one web app manifest file is specified:

`html example ... ...`

`$3`

`html example ... ...`

`How to use this hint?`

This package is installed automatically by webhint:

`bash npm install hint --save-dev`

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

`json { "connector": {...}, "formatters": [...], "hints": { "manifest-exists": "error", ... }, "parsers": [...], ... }`

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

@hint/hint-manifest-exists

Has web app manifest (`manifest-exists`)

Why is this important?

What does the hint check?

$3

`$3`

`How to use this hint?`

Further Reading

@hint/hint-manifest-exists

Has web app manifest (`manifest-exists`)

Why is this important?

What does the hint check?

$3

`$3`

`How to use this hint?`

Further Reading

@hint/hint-manifest-exists

Has web app manifest (manifest-exists)

Why is this important?

What does the hint check?

$3

$3

How to use this hint?

Further Reading

@hint/hint-manifest-exists

Has web app manifest (manifest-exists)

Why is this important?

What does the hint check?

$3

$3

How to use this hint?

Further Reading

Has web app manifest (`manifest-exists`)

`$3`

`How to use this hint?`

Has web app manifest (`manifest-exists`)

`$3`

`How to use this hint?`