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

frui

v0.1.3

Published

A collection of vanilla react components written in typescript.

Downloads

9

Readme

JUST REACT COMPONENTS

No layouts, no grids, no themes, no style engine, no design system. FRUI offers a comprehensive suite of free react components to use without the commitments. Checkout the Examples

Install

$ npm install frui

Contributing

Thanks for being an awesome developer! We are always looking for contributors and sponsors. If your interested, contact us so we can discuss. Clone this repo and run the following commands in the project folder.

$ yarn
$ yarn build
$ yarn dev

Please follow the steps below to properly contribute to this repository.

Do not commit code that is not related to a GitHub issue!

Please tag all your commits with [type]/[issue#].

Please include the time it took per commit. ie. 1s or 1h.

  1. Per issue on Github, you should create a branch. example: [type]/[issue#]
    • Per feature you should create a feature branch. ie. feature/1001.
    • Per bug you should create a fix branch. ie. fix/1002.
    • Per task you should create a task branch. ie. task/1003
  2. Commits need to reference the issue that is being worked on. example: updated copy #1004 or fixes #1005
    • It's also good to to add the amount of time to your commit message. example: fixed button #1006 30m or built awsome feature #1007 16h
  3. When you are finished with your branch, you should create a pull request back to the main branch.
    • Assign another developer to review your code.
    • All contributors are expected to both write and review code.
    • Ask Dev lead for assignments.