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-no-friendly-error-pages

v3.3.26

Published

hint that that checks if protocol relative URLs are used

Downloads

62,552

Readme

No small error pages (no-friendly-error-pages)

no-friendly-error-pages warns against using custom error pages with byte size under a certain threshold.

Why is this important?

Internet Explorer 5-11 will show its custom error pages instead of the site provided ones to avoid terse server error messages such as Error - 400 being shown to users.

The custom error pages are displayed whenever the response body’s byte length is shorter than:

  • 256 bytes for responses with the status code: 403, 405, or 410
  • 512 bytes for responses with the status code: 400, 404, 406, 408, 409, 500, 501, or 505

Similar behavior existed in older versions of other browsers, such as Chrome.

Although it's possible for users of Internet Explorer to disable the Show friendly HTTP error messages functionality, it is not typical.

What does the hint check?

The hint looks at all responses and checks if any of them have one of the status codes specified above and their body’s byte length is under the required threshold.

Additionally, the hint will try to generate an error response (more specifically a 404 response), if one wasn’t found.

Examples that trigger the hint

Response with the status code 403 and the body under 256 bytes:

HTTP/... 403 Forbidden

...
<!doctype html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>403 Forbidden</title>
    </head>
    <body>This page has under 256 bytes, so it will not be displayed by all browsers.</body>
</html>

Response with the status code 500 and the body under 512 bytes:

HTTP/... 500 Internal Server Error

...
<!doctype html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>HTTP 500 - Internal Server Error</title>
    </head>
    <body>
        <h1>HTTP 500 - Internal Server Error</h1>
        <p>This page has under 512 bytes, therefore, it will not be displayed by some older browsers.</p>
    </body>
</html>

Examples that pass the hint

Response with the status code 403 and the body over 256 bytes:

HTTP/... 500 Internal Server Error

...
<!doctype html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>HTTP 403 - Forbidden</title>
    </head>
    <body>
        <h1>HTTP 403 - Forbidden</h1>
        <p>......................................................................</p>
        <p>This page has over 256 bytes, so it will be displayed by all browsers.</p>
        <p>......................................................................</p>
        <p>......................................................................</p>
    </body>
</html>

Response with the status code 500 and the body over 512 bytes:

HTTP/... 500 Internal Server Error

...
<!doctype html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>HTTP 500 - Internal Server Error</title>
    </head>
    <body>
        <h1>HTTP 500 - Internal Server Error</h1>
        <p>......................................................................</p>
        <p>This page has over 512 bytes, so it will be displayed by all browsers.</p>
        <p>......................................................................</p>
        <p>......................................................................</p>
    </body>
</html>

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": {
        "no-friendly-error-pages": "error",
        ...
    },
    "parsers": [...],
    ...
}

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

Further Reading