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

@berlitz/not-found-layout

v3.4.3

Published

NotFoundLayout component for the Max Design System

Downloads

6,426

Readme

NotFoundLayout npm version

The Not Found Layout component has been ported over from our first berlitz USA website. As a result we now have a reusable Not found template we can use for any future websites that require a 404 not found page. This currently takes 4 props. Heading, Subheading below the main heading, a content block of text, and backLink to take the user back home base on the prefix.

Installation

yarn add @berlitz/not-found-layout

Props

| Argument | Type | Required | Default | Example | | ------------ | ------ | -------- | ---------------- | ------------------------------------------------- | | heading | string | | "404" | | | subheading | string | | "Page not Found" | | | contentBlock | string | | | | | backLink | node | ✅ | | {backLink.title} |

exampleData.js

export default {
  heading: '404',
  subheading: 'Page not Found',
  contentBlock:
    '<p>We’re all for adventure… but this one has led you to a dead end.</p>',
  backLink: {
    label: 'Back to home',
    link: '/en-de',
  },
}

Usage

import React from 'react'
import NotFoundLayout from '@berlitz/not-found-layout'

const BackLink = () => <Link href={backLink.url}>{backLink.title}</Link>
const MyApp = () => (
  <NotFoundLayout
    heading={heading}
    subheading={subheading}
    contentBlock={contentBlock}
    backLink={<BackLink />}
  />
)

When to use this component

404 Pages