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

@buildo/bento

v15.0.1

Published

one lib to rule them all: components, data management, build scripts, example app template.

Downloads

29

Readme

Bento

one lib to rule them all: components, data management, build scripts, example app template.

Detailed documentatin is temporarily hosted here.

Usage

Starting a new project from scratch

Install the create-bento-app command globally:

yarn global add @buildo/create-bento-app

Create a new app:

create-bento-app my-app

Start development:

cd my-app
yarn start

Adding Bento to an existing project

yarn add @buildo/bento

Components

Bento exports a complete set of basic React components from @buildo/bento/components. You can import a component like so:

import Badge from '@buildo/bento/components/Badge'

Read more about how to import and customize a Bento components in the detailed documentation.

Go to http://react-components.buildo.io/ to read docs and see a live demo for every React components exported by Bento.

Utils

MobileDetect

Import:

import MobileDetect from '@buildo/bento/utils/mobileDetect';

const md = new MobileDetect(/* optional: pass custom user agents */)

Please refer to MobileDetect GitHub repository for documentation and examples.

LocalDate

Import:

import LocalDate from '@buildo/bento/utils/localDate'

Please refer to local-date GitHub repository for documentation and examples.

Theme

normalize-css

CSS normalizer based on buildo-normalize-css

Usage:

import 'bento/theme/normalize-css'

NOTE: If your app is fullscreen, you need to import the fullscreenApp module too:

import 'bento/theme/normalize-css'
import 'bento/theme/normalize-css/fullscreenApp'

Bitbucket sync procedure

Assuming two folders inside the same directory, bento (this repo) and bento-bitbucket (bitbucket ~mirror)

  • [ ] cd bento-bitbucket && gco master
  • [ ] update bento code (including deps, src, create-bento-app template, etc.) rm -rf ./* && cp -r ../bento/* .
  • [ ] be sure to copy correctly also any added .dotfiles (the command above doesn't)
  • [ ] some files should not be copied: gco -- README.md publish.sh
  • [ ] check with diff --brief -Nr --exclude=node_modules --exclude=.git --exclude=*.tgz --exclude=*.log . ../bento: only a few files should differ (README, CHANGELOG, publish.sh, .hophoprc, .smooth-releaserc)
  • [ ] git add . && git commit -m "github sync"
  • [ ] update the release branch with the new additions: gco release && git merge master
  • [ ] fix the react-components dep: yarn remove buildo-react-components; yarn add --no-lockfile ssh://[email protected]/ben/abbott-react-components.git
  • [ ] update all the imports from react-components to refer to abbott-react-components: e.g. search&replace buildo-react-components -> abbott-react-components
  • [ ] manual fixes.. try to build and fix errors
  • [ ] manual additions.. some components might be available only in abbott-react-components (or viceversa)
  • [ ] when build is fine, git push origin release
  • [ ] (OPTIONAL) release a new version ./publish.sh <versionNumber>-abbott <-- version number should be updated manually. It should reflect current @buildo/bento version (except for the -abbott suffix that is added)