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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@asnewyla/unstyled-radio

v0.2.0

Published

Unstyled radio input primitive with accessibility

Readme

@asnewyla/unstyled-radio

Unstyled, accessible radio input primitive. Handles checked, focus, and invalid-state tracking without imposing any visual styling — the base layer under @asnewyla/radio.

Install

npm install @asnewyla/unstyled-radio

Usage

import { UnstyledRadio } from '@asnewyla/unstyled-radio';

// Uncontrolled — a single radio, or a group sharing a native `name`
<UnstyledRadio aria-label="Option A" name="choice" defaultChecked />
<UnstyledRadio aria-label="Option B" name="choice" />

// Controlled
<UnstyledRadio
  aria-label="Option A"
  checked={selected === 'a'}
  onChange={() => setSelected('a')}
/>

// Invalid state
<UnstyledRadio aria-label="Option A" invalid />

Props

| Prop | Type | Default | |---|---|---| | checked / defaultChecked | boolean | — | | onChange | (event: React.ChangeEvent<HTMLInputElement>) => void | — | | disabled | boolean | false | | invalid | boolean | false |

Uncontrolled by default, same as a native <input type="radio"> — pass checked + onChange to control it yourself.

State is exposed via data-checked, data-focused, data-disabled, and data-invalid/aria-invalid — style off these attributes rather than :checked, for the same DevTools-visible, test-stable reasons every other @asnewyla/* primitive uses data-* for state.

A real multi-radio group needs RadioGroup, not several bare UnstyledRadios

Two UnstyledRadios sharing a native name get correct browser-level exclusivity for free — clicking one genuinely unchecks the other at the DOM level, no JavaScript required. But each UnstyledRadio only learns about its own checked state through its own onChange; browsers never fire a change event on a radio that gets deselected as a side effect of a sibling being selected. That means data-checked on the deselected radio goes stale — the underlying <input> really is unchecked, but the attribute you'd style off doesn't know it yet.

For a real, visually-correct multi-radio group, use RadioGroup (a shared source of truth for which value is selected) rather than several independent, uncontrolled UnstyledRadios. UnstyledRadio on its own is reliable for a single isolated radio, or for any usage where you fully control checked yourself.

License

MIT