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

@clowdr-app/amazon-chime-sdk-component-library-react

v2.2.1

Published

Amazon Chime SDK Component Library - React

Readme

Amazon Chime SDK React Components Library

Amazon Chime SDK React Components Library Documentation

Amazon Chime SDK for JavaScript Library

The Amazon Chime SDK makes it easy to add collaborative audio calling, video calling, and screen share features to web applications by using the same infrastructure services that power millions of Amazon Chime online meetings.

The Amazon Chime SDK React Component Library supplies client-side state management and reusable UI components for common web interfaces used in audio and video conferencing applications, including: video tile grids, microphone activity indicators, and call controls. All components come with a simple, modern design, and can be used as-is or restyled with a custom theme. In addition to UI components, the library leverages Reacts' state management tools such as Providers and Hooks to connect to the Amazon Chime SDK for JavaScript and pass data to the UI layer, simplifying state synchronization so that developers can concentrate on building engaging experiences.

The Amazon Chime React Component Library can be added to your web application codebase using npm.

Documentation on these components and how to use them can be found on Amazon Chime SDK React Component Library Documentation.

To get started, see the following resources:

Amazon Chime SDK

Amazon SDK Pricing

Supported Browsers

Amazon Chime API Reference

Amazon Chime SDK for JavaScript Documentation

Migration from V1 to V2

Examples

Meeting Demo

Chat Demo

Installation and Development

If you are adding this library to your existing application, add amazon-chime-sdk-component-library-react and the necessary peer dependencies to your project.

npm install --save amazon-chime-sdk-component-library-react amazon-chime-sdk-js styled-components styled-system 

Otherwise clone the repo and install the dependencies.

Contributing to the component library

To generate dependencies

git clone https://github.com/aws/amazon-chime-sdk-component-library-react.git
npm install

To run the Storybook server locally

npm start

Build

npm run build

Once you build, check and resolve any warnings you may get like unresolved dependencies or circular dependencies. Remove these as it will help in bundling the library warning/error free.

Test

Run all unit test suites.

npm run test

Run an individual unit test suite.

npm run test -- <filepath>

Run all unit test suites in watch mode

npm run test -- --watch

Run all snapshot test suites. Docker is required to run Puppeteer in a Docker container.

npm run test:snapshots

Troubleshooting

Error 1: Service 'chromium' failed to build : toomanyrequests: You have reached your pull rate limit

You may need to create a Docker Hub account and authenticate pull request from Docker Hub. Unauthenticated (anonymous) users will have the limits enforced via IP.

Error 2: Timeout when you run npm run test:snapshots

You have 2 options:

  1. Set an environment variable WAIT_ON_TIMEOUT=600000 (e.g. 10 minutes. By default, it's 5 minutes). It will wait for a longer time while checking for the server to respond.
  2. Start storybook server locally by running npm start, then run npm run test:snapshots.

Run an individual snapshot test suite, make sure that storybook server is running locally before kicking off the test.

npm run test:snapshots-path -- <filepath>

Run an individual snapshot test suite and override existing snapshot(s).

npm run test:snapshots-path -- <filepath> -u

A code coverage summary will be printed at the end of each npm run test run. Full coverage including coverage for each file is generated in a lcov-report html file that can be rendered in the browser. This is generated in a /coverage directory on each test run.

License

This project is licensed under the Apache-2.0 License.

Copyright 2020-2021 Amazon.com, Inc. or its affiliates. All Rights Reserved.