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

@staccx/bento

v13.7.2

Published

![Bento logo](https://cdn.sanity.io/images/8j24leyc/production/4fdac3349ebe1799c7104608a6cd9727fb9e25f9-2188x1378.png)

Downloads

875

Readme

Bento logo

What is Bento?

Bento is a set of UI components, utility functions, hooks, and other reusable parts that make up your typical React project. There are also some utilities that are made for our customers in the financial sector. When developing Bento we set out to solve some issues we had with other alternatives:

  • Theming. No more having to fight with all the styles you don't want when trying to create a user interface. Nothing that prevents you from getting things exactly like you want them.
  • A11y. Components should not be inaccessible by default. And should never get in the way of making something more accessible.
  • Reusability. Good frontend code is hard, why reinvent the wheel every time you need to do the stuff you do again and again.

Because we want to spend our time writing the code we need, instead of overriding the code we don't need, Bento is pretty barebones in the visual department. Do not use Bento without creating your own theme.

No conflicts

Bento depends on styled-components being available in your app. That doesn't mean you have to use styled-components everywhere in your app, but it does mean that Bento's styles won't conflict with other CSS in your app. There are a lot of things that could be bundled with Bento that we've chosen to leave out. You need to choose your own solution for things like state management, routing and data fetching. Bento is made to fit in with different approaches to these things instead of forcing you to use any particular solution.

Server-side rendering

Most parts of Bento will work just fine with SSR if you set up SSR with styled-components correctly.

Licenses

Bento is proprietary. It is not intended for public use. If you want to use Bento without a prior agreement with Stacc X, please get in touch with us and we'll figure something out.