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

@web-fuse/wf-components

v1.0.9

Published

A library containing common form and display components

Vulnerabilities

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

Links

Git

Maintainers

luc.aluc.a

Keywords

Readme

Web-Fuse Components

A library containing common form and display components. The component requires that you use the React Framework and relies on styled-components and antd packages. If you want to use the CodeBlock you will also need to install react-copy-to-clipboard and react-syntax-highlighter.

Previewing components

You can preview and test the components by cloning the repository to your system and running storybook.

  1. Clone this repository to your system
  2. Open the directory in a terminal
  3. Install all dependencies by running npm install in the terminal
  4. To start storybook run npm run storybook

Local development

To make changes in the repository you should first run storybook as explained in Previewing Components. Open the component you want to edit in storybook and navigate to the corresponding file in the src directory. Each component will have its own file or files. Stories are located in the src/stories directory.

Each component must always be exported using export default and each component must always be assigned to a const variable before it is exported. If this is not done vite may have problems rebuilding the component and React will not know the name of the component.

Ant design global message API

You can create a global context for the ant design message API by using the MessageProvider component. The messages can be styled by placing the ConfigurationProvider higher in the component tree and customizing the theme. Use the useMessageApi hook to access the message API and show message to the user.

It is currently not possible to create nested MessageProviders.

Custom theme algorithm for antd

If you are using the theme.darkAlgorithm in your antd ConfigProvider you may notice that your primary color is not preserved. Therefor this package includes the wfDarkAlgorithm export. The only change, compared the the darkAlgorithm exported by antd, is that it takes retains your primary color.