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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@otosense/components

v0.2.6

Published

## Use yarn link to real-time modification

Downloads

30

Readme

OtoSense Design Library

Use yarn link to real-time modification

  1. make sure you have yarn installed (npm i -g yarn) yarn install
  2. yarn pack-copy
  • if tsc is not found, run npm install -g typescript and try again

if tsc runs correctly: 3. in the components directory, yarn link 4. in QC at client, yarn link @otosense/components (edited) 5. to update, run yarn pack-copy

Material-UI themes and shared view components.

  • Use import

Usage

Buttons

variants: 'contained' (default), 'outlined', 'text' color: 'primary', 'secondary', 'error', 'success', 'info', 'warning', 'cancel', 'critical', 'gray' size: 'small', 'medium', 'large'

  • default is color='primary', variant='contained', and size='medium'. You don't need to write these.
  • Please see Figma file to refer all the variants and color options

Select

Select field is styled in Form Control. Use default and apply size props in the Form Control (not Select) component. Most of the time, we need Typography component with variant overline which is styled for this.

Example: {header} <Select value={value} onChange={handleChange}

{options.map((name, j) => {
  return (
    <MenuItem key={`assettype-option-${name}-${j}`} value={name}>
      {name}
    </MenuItem>);
})}

Dialog

  • use with DialogTitle, DialogContent, and DialogActions to have right spacings.

Header component takes props below:

version: string | number; account: string; logout: VoidFunction; currentDateTime: string; isLoginModeOnline: boolean; setCurrentUserSession: VoidFunction; toggleDateTimeFormat: VoidFunction; #change local or UTC languageOptions: string[]; #available locales localeFc: any; #the locale function textVersion: string; locale: string; #current locale textLogout: string; setCurrentTimestamp: () => void; logoFile: string;


OtoModal component takes props below *children is passed automatically

  • please use Dialog for general use. This may be deleted.

    onClose: VoidFunction; label?: string; id?: string; children: JSX.Element;