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

@hyperfixi/speech

v7.6.0

Published

The speak command (Web Speech API) for @hyperfixi/engine, as an engine module (upstream _hyperscript 0.9.90).

Readme

@hyperfixi/speech

The speak command for @hyperfixi/engine: upstream _hyperscript's command (0.9.90), as an engine module. It speaks text through the Web Speech API and waits until the utterance ends.

speak "Welcome back"
speak "Hello" with rate 1.5 with pitch 0.8
speak "Bonjour" with voice "Google français"
speak "Saved" then put "done" into #status    -- `put` runs once the speech has ended

Install

An engine is the list of modules passed to register; add speak to it:

import { boot, everything, register } from '@hyperfixi/engine';
import { speak } from '@hyperfixi/speech';

register(...everything, speak);
boot();

The script-tag bundle (hyperfixi-hs.js) is a fixed set of modules and does not include it.

Options

Each option follows its own with, in any order:

| Option | Notes | | -------- | --------------------------------------------------------------------------------------------------- | | voice | Matched against speechSynthesis.getVoices() by .name. A voice that is not installed is ignored. | | rate | SpeechSynthesisUtterance.rate. Browser default 1; valid range typically 0.1 – 10. | | pitch | SpeechSynthesisUtterance.pitch. Browser default 1; valid range typically 0 – 2. | | volume | SpeechSynthesisUtterance.volume. Browser default 1; valid range 0 – 1. |

Another word after with is a parse error that names the four.

ask and answer

Upstream's two dialog commands are in the engine already (its askAnswer module, part of everything): ask "Name?" prompts and puts the reply in it; answer "Saved" alerts; answer "Save?" with "Yes" or "No" confirms and puts the choice in it.

Notes on browser support

  • Voices load asynchronously on some browsers: a with voice given before they load falls through to the default.
  • iOS Safari speaks only after a user gesture: run speak from a click handler, not on load.
  • Where the Web Speech API is missing, speak fails the way upstream's does (the handler reports the error).

Exports

  • speak (also the default export): the module, (grammar) => void.
  • SpeakNode: the type of the parsed command.

4.0

Until 4.0 this package was a plugin for @hyperfixi/core's runtime: speechPlugin, installed with installPlugin, with its own ask (with default …) and answer with "x", which set the result without a dialog. Core's runtime is gone; upstream's ask / answer are the engine's, and speak behaves as upstream's does (it waits for the speech to end, and no longer sets result).

License

MIT