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

@defogdotai/agents-ui-components

v1.0.4

Published

## Quickstart

Downloads

1,172

Readme

agents-ui-components

Quickstart

Usage

Run npm run storybook and go to the Quickstart page for instructions.

Test things locally

First, do:

npm i
npm run dev

Now, create a .env file in your root directory with the following content, where HASHED_PASSWORD and API_ENDPOINT are replaced by actual values.

VITE_TOKEN="HASHED_PASSWORD?"
VITE_API_ENDPOINT="API_ENDPOINT"

Open http://localhost:5173 in your browser, and select one of the components to see it in action.

Corresponding code for all those pages is inside test/ folder.

Publishing to npm

First, create a build with npm run build. This will automatically create a dist folder. Then, run npm run publish

Viewing docs

Run npm run storybook to see detailed documentation.

Running tests

Quick:

To run all tests in a bagkround browser: npx playwright test

Semi quick:

To run all tests and also watch them happen in the browser: npx playwright test --headed

Manual:

To manually run tests: npx playwright test --ui

Debugging:

To debug tests, I recommend following this guide: https://playwright.dev/docs/debug

(Using the VS Code extension might be the best option).

Here's a loom video showing how you can debug your tests: https://www.loom.com/share/a4c05d41dced4855a525634f310b1449