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

react-faux-button

v1.0.0

Published

An accessible, configurable React Button usurper.

Downloads

11

Readme

React Faux Button

Accessible React <button> usurper.

npm gzip size npm downloads

Table of Contents

NOTE

Use sparingly. If you can use the default <button> – possible more often than not – just do so. Incidentally, this is the reason the package is called "faux" button :)

Features

  • Accessible defaults.
  • Full presentational control for the caller.
  • Easy to understand source code. You should be able to fork and do your thing if desired.
  • Ample documentation to help you understand the problem, in addition to the solutions.

What it does not do by itself:

  • Style things. That is up to you :)

Install

This package is distributed via npm.

$ npm install --save react-faux-button
# or
$ yarn add react-faux-button

Then import according to your modules model and bundler, such as Rollup and Webpack:

// ES Modules
import { FauxButton } from "react-faux-button";

/// CommonJS modules
const { FauxButton } = require("react-faux-button");

A UMD version is also available on unpkg:

<script src="https://unpkg.com/react-faux-button/dist/react-faux-button.umd.js"></script>

Motivation

When having an interactable item in your application, a button is almost always the right answer. I have found that many developers are averse to using button due to its historical styling issues.

While I find the button resets (and more importantly, styling) to be straightforward nowadays, I often have to work with codebases that use divs with an onClick. Those codebases might have non-straightforward resets, might rely on the element being a div, and so on. In those cases, I find it particularly useful to have an accessible button usurper. This is the one I use.

Usage

Quick Start

If you want to just dive in, do this:

import { FauxButton } from "react-faux-button";

<FauxButton tag="div" onInteraction={() => /* do something */}>
  Print files
</FauxButton>

References

The ARIA authoring practices offer a concise overview of expected button behaviour:

  • https://www.w3.org/TR/wai-aria-practices-1.1/#button
  • https://www.w3.org/TR/wai-aria-practices-1.1/examples/button/button.html