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

@demo-uikit-zs/uikit

v0.0.4

Published

UI toolkit monorepo containing a React component library, UI utilities, a drag-and-drop library, and more

Downloads

7

Readme

UIKit

Build and Test results Top language Commits per month

UI toolkit monorepo containing a React component library, UI utilities, a generative AI LLM parser, an AWS AppSync fetch utility, and more

Packages

| NPM Package Name | Version | Description | |------------------------------| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | [@acusti/input-text][] | latest version | A promise-based node.js function for making AWS AppSync API graphql requests | | [@acusti/input-text-2][] | latest version | An isomorphic module implementing the [AWS Signature V4 (SigV4) signing process][aws sigv4] for requests |

The React components are documented and illustrated in the storybook instance, which is located at packages/docs/ in the repository.

Tests

The monorepo uses vitest to run its tests. To run tests across all packages, use yarn test. To run them in watch mode, use yarn test:watch.

Building and Publishing

To build all packages, run yarn build. This will trigger tsc --build and yarn flowgen for all packages.

To build the storybook docs, run yarn build:stories, which will run yarn build and then the default storybook build command.

To publish all packages, manually update each packages’s version field in their package.json. If any of the packages depends on any of the other packages being updated, be sure to update the dependency version as well. Then run yarn publish. Publishing will trigger a build before running npm publish to ensure that the latest changes are published. To publish only a single package, use yarn workspace <package-name> npm publish --access public (e.g. yarn workspace @acusti/css-value-input npm publish --access public), but note that in that case, you are responsible for running yarn build yourself before triggering the publish.

After publishing the packages, run yarn to update the yarn.lock file and then commit the version updates with a message in the form of: :arrow_up: Bump package versions to _._._.

Developing

The two main run scripts for developing are yarn dev:watch, which kicks off the TypeScript compiler in --watch mode, and yarn dev:stories, which kicks off the default storybook command from packages/docs/. To run both of those in a single terminal window, use yarn dev.