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

botframework-webchat-chat-adapter

v0.0.3-main.058f2a2

Published

``` _ _ _ _ _ _ ___| |__ __ _| |_ __ _ __| | __ _ _ __ | |_ ___ _ __ _ __ _ __ ___ | |_ ___ | |_ _ _ _ __ ___ / __| '_ \ / _` | __| / _` |/

Downloads

126

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

earliestearliest

Keywords

Readme

      _           _               _             _                              _        _                    
  ___| |__   __ _| |_    __ _  __| | __ _ _ __ | |_ ___ _ __   _ __  _ __ ___ | |_ ___ | |_ _   _ _ __   ___ 
 / __| '_ \ / _` | __|  / _` |/ _` |/ _` | '_ \| __/ _ \ '__| | '_ \| '__/ _ \| __/ _ \| __| | | | '_ \ / _ \
| (__| | | | (_| | |_  | (_| | (_| | (_| | |_) | ||  __/ |    | |_) | | | (_) | || (_) | |_| |_| | |_) |  __/
 \___|_| |_|\__,_|\__|  \__,_|\__,_|\__,_| .__/ \__\___|_|    | .__/|_|  \___/ \__\___/ \__|\__, | .__/ \___|
                                         |_|                  |_|                           |___/|_|

Etqiuette

Test for every fix and feature

This section is not completed yet.

All fix and feature work must come with integration tests. This is to protect your code and make sure your investment will not be broken by others.

Please review our tests under __tests__/stories. These tests are user stories. They include both "today's requirements" and "tomorrow's dreams". We try to push this adapter design to as far as 2 years ahead.

For every new feature, a user story is required. The user story need to be coded as an end-to-end test and placed under this folder for POR.

Design

Egress design

Goals

TODO: Add links to user stories

  • Middleware/enhancer can patch/skip/fork egress activities
    • Asynchronous patch
    • Can be skipped
    • Can be forked into 2+ activities

Ingress design

Goals

TODO: Add links to user stories

  • Anyone who have public access to adapter can send ingress
  • Middleware/enhancer can stop ingress of another middleware/enhancer
    • Web Socket can pause/resume REST API (protocol fallback)
    • Connection manager can stop downstream ingress
  • Middleware can patch/skip/fork the activity of another middleware doing the ingress

Optional goals

  • Easy to ingress a static transcript

Other designs

  • Event target and async iterables are recommended, Observable is welcomed
  • Do not use any operators on Observable
    • Observable operators (for example, flatMap and retryWhen in RxJS) are not welcomed because they are very difficult to debug

Related articles