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

@wee-busines/wee-error-pages

v1.0.1

Published

Error pages for all wee apps

Downloads

1

Readme

wee-error-pages

Error pages for all wee apps

Install

yarn install wee-error-pages --save yarn add wee-error-pages

Usage

import * as React from 'react'

import { ErrorPagesContext } from 'wee-error-pages';
import { ResourceNotFound } from 'wee-error-pages';
import { ServerError } from 'wee-error-pages';

class Example extends React.Component {
  render () {
    return (
      <ErrorPagesContext.Provider value={{ language: 'de' }}>
        <ServerError backUrl="#login"/>
        <ResourceNotFound backUrl="#" />
      </ErrorPagesContext.Provider>
    )
  }
}

Running in development mode

Run wee-error-pages

Go to project root directory and run

yarn start

Run Example project

In a new command line terminal go to example directory and run

yarn start

In your browser go to localhost:3000 and see the example project in action. You can make changes in the library and view changes in the browser in your example project.

Building and testing library using yarn link.

If you only want to test the wee-error-pages component in your project you can build the library by running

yarn build

And then link the library using

yarn link

In the project where you want to test the components run following command

yarn link "wee-error-pages"

Now run your project and you will be able to test the library without downloading it from npm repo. This method is particularly useful when you just want to test the components locally when they are not available in npm repo.