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

qwil-react-components

v1.114.0

Published

Qwil React Components

Downloads

244

Readme

Qwil React Components

General Shared React components for Qwil

Installation

yarn add qwil-react-components

##Components

All components must be implemented under src/components folder with its own folder, e.g Button component will live in src/components/Button. Each component must have a <componentName>.md file, like Button.md which will have a description of how to use it including the example code.

For information about how document a component, see here.

Components styles

Each component must have a <componentName>.scss file and a file per tenant to specify the variables it will use which have different values for each tenant. Example:

Button.scss

Button.qwil.scss

Button.cambridge.scss

See Build section for available tenants.

Documentation

The project uses Storybook. The use of it is part of the development process since will allow you to create your components and see it live with the documentation and the running example.

here

Build

dev and prod builds must specify a tenant to use. By default qwil is set.

Available tenant:

  • qwil
  • cambridge

Build for prod

This will produce the index.js file to be publish and will generate the documentation too (yarn docs)

yarn build

The build is output in dist folder and the bundle is a UMD module.

build for testing in the webapp

This will produce the same bundle as for prod but it will generate the source maps inside the bundle. DO NOT USE IT FOR PROD BUILD.

Build documentation

yarn docs

The docs are generated under styleguide folder.

Dev server

To start the server run:

yarn start

It will start the dev server in watch mode in http://localhost:6060/. You can change the port in styleguide.config.js under serverPort prop. The dev server will compile your components and render the documentation with the live examples.

Deployment

make ship tag={a_tag}