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

@mashroom/mashroom-error-pages

v2.7.1

Published

Mashroom middleware to show proper HTML pages for arbitrary HTTP status codes (e.g. 404)

Downloads

99

Readme

Mashroom Error Pages

Plugin for Mashroom Server, a Microfrontend Integration Platform.

This plugin allows it to show proper HTML pages for arbitrary HTTP status codes. It delivers error pages only if the request accept header contains text/html. So, typically not for AJAX requests.

Usage

If node_modules/@mashroom is configured as plugin path just add @mashroom/mashroom-error-pages as dependency.

You can override the default config in your Mashroom config file like this:

{
  "plugins": {
        "Mashroom Error Pages Middleware": {
            "mapping": {
                "404": "./pages/404.html",
                "403": "./pages/403.html",
                "400": "http://my.server-com/bad_request.html",
                "500": "/some/server/path/500.html",
                "default": "./pages/default.html"
            }
        }
    }
}
  • mapping: Maps status codes to error pages. The target files can be file paths or HTTP/S urls. If the file path is not absolute the plugin will expect it to be relative to the plugin folder or the Mashroom server config file. If a status code is not defined in the mapping or no default exists, no error page will be shown.

HTML Files

  • The HTML files should not reference local resources (Images, CSS, JavaScript) because they cannot be loaded
  • They may contain the following placeholders:
    • $REQUEST_URL: The original request URL
    • $STATUS_CODE: The status code
    • $MASHROOM_VERSION: The Mashroom Server version
    • $MESSAGE[messageKey(,Default text if i18n not yet available)]: A translated message from the mashroom-i18n package