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

slackers

v0.2.0

Published

Simple 'end of the road' pages with good modern vibe

Downloads

3

Readme

Slackers

Slackers are simple amusing pages to use as placeholders with no effort.

The pages are valid components for preact.

there is also a demo.

What is it good for?

well, you can use them for any purpose really. I use them as placeholders for dark corners of my SPA where in normal case you should never get to but its in-fact possible. For example:

when using react-router or so.. a catch all page ('*') can take not-found.

Or when an evil user navigates manually to authenticated user area only (unauthorized)

Usage

Install using npm

npm i -S slackers 

Simple render

import NotFound from 'slackers/not-found';
// or
var NotFound = require('slackers/not-found');

render(h(NotFound), target)

Change text:

render(h(NotFound, {
    text: "This page doesn't exist"
  }), target)

Change icon:

import Base from 'slackers/base'

let backgroundImage = '' // path or base64 content (using webpack require for example)

render(h(Base, {
    backgroundImage,
    text: "My custom text"
}), target)

As standalone script (not recommended)

<script src="https://unpkg.com/slackers/standalone/slackers_not-found.js"></script>
<script>
  var NotFound = window['slackers_not-found'];
</script>

Example

import {render, h} from 'preact';
import NotFound from 'slackers/not-found';
render(h(NotFound), target)

Will render:

not-found

Current list of available slackers

  • not-found
  • unauthorized
  • error
  • maintenance
  • loader (animated)
  • loader-gears (animated)

Credits