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

zapkeys

v0.2.1

Published

> The simplest way to make all your site’s interactions into keyboard shortcuts

Downloads

112

Readme

ZapKeys

The simplest way to make all your site’s interactions into keyboard shortcuts

Give your users the ability to efficiently navigate and interact with your whole site using only their keyboards. Turn them into power users. ⌨️

What it does

With ZapKeys, users will be able to press F (or any other letter key; it's configurable), and every interactive element on the page – links, buttons, textareas, inputs – will be highlighted with a letter/sequence. Users can then press an element's letter/sequence and it will trigger that element's interaction – clicking on links and buttons, or focusing on inputs.

With minimal effort, your site becomes completely usable with only the keyboard.

Users don't need to figure out nor remember specific shortcut sequences and you don't have to configure them.

Framework-agnostic

ZapKeys works directly on top of the DOM. So it does not matter how the DOM is generated. This means it can work alongside any framework or library like React, Vue, Ember, Angular and any other or none at all.

Simplest Usage

  1. For the functionality, in your javascript:

    const shortcuts = new ZapKeys();
    shortcuts.init();
  2. For the styles:

    @import '~zapkeys/index.css';

    or in your JS:

    import '~zapkeys/index.css';

Custom Configuration

Functionality

ZapKeys has a few configuration options, during instantiation:

| Option | Description | Default | | ------------------------ | ----------------------------------------------------------------------------------------------------------------- | ------- | | startKey: string | The key what activates the shortcuts. Only supports single keys. | "f" | | onActive: () => void | Function to execute when ZapKeys is active; when the start key has been pressed and the elements are highlighted. | none | | onInactive: () => void | Function to execute when ZapKeys becomes inactive; after an element has been triggered by a letter/sequence. | none |

To customize these, pass them during instantiation:

const sk = new ZapKeys({
  startKey: 'x',
  onActive: () => console.log('It is active!'),
});

Styling

ZapKeys includes nice defaults styles for the shortcut letter indicators, but if you'd like to customize them, you could do so by:

  1. Not importing the ~zapkeys/index.css file into your styles, and instead copying the CSS from it into your own, and

  2. Updating the .__zk-letter styles to your heart's content:

    /* ...rest of the styles remain the same... */
    
    .__zk-letter {
      /* remove the default styles and your custom styles here */
    }
    
    /* ...rest of the styles remain the same */