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-speech-recognizer-component

v1.0.7

Published

React component for Speech Recognition based on Speech Recognition Web API.

Downloads

20

Readme

react-speech-recognizer

React Component for Speech Recognition.

This HOC component allows to get Speech Recognition capabilities into your app. By wrapping your component on it, you can have it changing depending on the transcripts you get back or the SpeechRecognizer.status.

It relies on the Web Speech Recognition API and if it's not supported in the browser, it logs a warn, renders nothing and calls the onError prop (if provided).

It creates a SpeechRecognition instance internally and exposes its events through props in the component.

Use it like:

import React from 'react';
import logo from './logo.svg';
import './App.css';

import { SpeechRecognizer } from 'react-speech-recognizer-component';

function App() {
  return (
    <div className="App">
      <h1>Speech to text test with React Speech Recognizer</h1>
      <SpeechRecognizer
        startSpeechRecognition={true}
        onError={this.onError}
      >
          {({status, results, formattedResults, transcripts, error}) => {
            return (
              <>
                {transcripts && transcripts.length && <p>{transcripts.join(', ')}</p>}
              </>
            );
          }}
      </SpeechRecognizer>
    </div>
  );
}

export default App;

props

Same as the ones that the SpeechRecognition object would accept, plus the one that says start recognizing, yo!.

  • startSpeechRecognition: flag that if true the recoznizer starts attempting to listen on your microphone.
  • grammars: Accepts a string in the (beautiful!) JSGF Format.
  • continuous: Flag that if true more than one result per recognition is returned.
  • interimResults: Flag that if true returns results that are not final.
  • maxAlternatives: Yup, the most alternatives that can be returned. Keep in mind that setting continous to false (which is the default value)
  • lang: ISO string with the language.

(Some) of the SpeechRecognition events are also exposed as props.

  • onStart: Callback run on the onstart event of the SpeechRecognizer instance.
  • onError: Callback run on the onerror event of the SpeechRecognizer instance. One of the cases when this is executed when SpeechRecognition is not supported by the browser.

Next steps

  1. Probably start over with a different idea in mind, based on what I learn while working on Guess The Movie (repo here). It'd be a VoiceCommandRecognizer instead. :)