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/hint-manifest-app-name

v2.4.29

Published

hint for best practices related to the web app manifest's name and short_name members

Downloads

103,502

Readme

Manifest has name (manifest-app-name)

manifest-app-name checks if the name of the web application is specified within the manifest file.

Why is this important?

Browsers that support the web app manifest file will use the value of the name property (or short_name's value, when there is insufficient space) to display the name of the app in various places across the OS such as the list of apps installed, an app icon label etc.

If these properties are not defined, browsers will try to get the name from other sources such as the value of the application-name meta tag, <title>, or default to a specific value (e.g.: Untitled). This can lead to a bad user experience, as the app name may be truncated or wrong.

So, to reduce the risk of having the app name truncated, it's recommended to define the name property and keep its value under 30 characters, and if it’s over 12 characters, include a short_name property that is at most 12 characters.

Notes:

  • If the name property value is under or 12 characters, there is no need to provide the short_name property as browsers can use the value of name.

  • The 12-character limit is used to ensure that for most cases the value won’t be truncated. However, depending on other things, such as:

    • what font the user is using
    • what characters the web site/app name includes (e.g. i occupies less space than W)

    the text may still be truncated even if it’s under 12 characters.

  • The above recommended limits are set to be consistent with the native OSes and/or store limits/recommendations, e.g.:

What does the hint check?

The hint checks if a non-empty name member was specified and its value is under 30 characters.

If the name member is over 12 characters, or short_name is specified, the hint will also check if short_name has a non-empty value that is under 12 characters.

Examples that trigger the hint

Manifest is specified without name and short_name:

{
    ...
}

Manifest is specified with a name longer than 12 characters and no short_name:

{
    "name": "Baldwin Museum of Science",
    ...
}

Manifest is specified with a name longer than 30 characters:

{
    "name": "Baldwin Museum of Science - visit today!",
    "short_name": "Baldwin"
    ...
}

Manifest is specified with short_name longer than 12 characters:

{
    "name": "Baldwin Museum of Science",
    "short_name": "Baldwin Museum"
    ...
}

Examples that pass the hint

Manifest is specified with a name shorter than 30 characters and a short_name shorter than 12 characters:

{
    "name": "Baldwin Museum of Science",
    "short_name": "Baldwin"
    ...
}

Note: Not specifying a manifest file or having an invalid one are covered by other hints, so those cases won’t make this hint fail.

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-app-name": "error",
        ...
    },
    "parsers": [...],
    ...
}

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

Further Reading