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 🙏

© 2025 – Pkg Stats / Ryan Hefner

bonkers-ui

v2.0.2

Published

Bonkers ui library

Downloads

295

Readme

Recommended IDE Setup

Setup project

  • Use bun to install all dependencies with the frozen lockfile

    bun i
  • To run the storybook

    bun storybook
  • open http://localhost:6006/

For use in a consuming project

  • Install the component library with your desired package manager.

    • Insure autoprefixer, postcss and tailwindcss are installed
  • In your tailwind.config.ts, add the Bonkers-UI tailwind plugin to your plugins array. Note: the content array should include the path to the Bonkers-UI source files once installed.

import bonkersUiConfig from "bonkers-ui/plugin";

export default {
	content: [
		/* ...other directories containing Tailwind styled components/pages */
		"./node_modules/react-ui/**/*.{js,ts,tsx}",
	],
	plugins: [bonkersUiConfig],
};
import type { Config } from "tailwindcss";
import bonkersUiConfig from "react-ui/plugin";
import { PluginCreator } from "tailwindcss/types/config";

const config = {
	content: [
		/* ...other directories containing Tailwind styled components/pages */
		"./node_modules/react-ui/**/*.{js,ts,tsx}",
	],
	plugins: [
		bonkersUiConfig as { handler: PluginCreator; config?: Partial<Config> },
	],
} satisfies Config;

export default config;
  • Ensure that the tailwind directives are included in your main.css file
@tailwind base;
@tailwind components;
@tailwind utilities;
  • Please ensure that your tsconfig file is configured with moduleResolution set to Bundler or NodeNext (depending on your project setup) to allow for the Bonkers-UI types to be resolved. Example:
{
	"compilerOptions": {
		"target": "ES2020",
		"module": "ESNext",
		"strict": true /* Specify what module code is generated. */,
		"verbatimModuleSyntax": true,

		"esModuleInterop": true /* Emit additional JavaScript to ease support for importing CommonJS modules. This enables 'allowSyntheticDefaultImports' for type compatibility. */,
		"forceConsistentCasingInFileNames": true /* Ensure that casing is correct in imports. */,
		"skipLibCheck": true /* Skip type checking all .d.ts files. */,
		/* Bun Settings */
		"moduleResolution": "node",
		"noEmit": true,
		"allowImportingTsExtensions": true,
		"moduleDetection": "force",
		"resolveJsonModule": true,
		"isolatedModules": true,
		"jsx": "preserve"
	},
	"include": ["src/**/*.ts", "src/**/*.d.ts", "src/**/*.tsx"],
	"references": [{ "path": "./tsconfig.node.json" }]
}
  • Bonkers-UI has been successfully installed to your project, now import any components you need!
import React from "react";
import { UiButton, EButtonTypes, EButtonSizes } from "bonkers-ui";
import { EInputKinds } from "bonkers-ui/types";

export type TNewComponent = {
	placeholder: string;
	heading: string;
	subLabel?: string;
	children: React.ReactNode;
};

export const NewComponent: React.FC<TNewComponent> = ({
	children,
	placeholder,
	heading,
	subLabel,
	...props
}) => (
	<div {...props}>
		<UiButton size={EButtonSizes.LARGE} kind={EButtonTypes.PRIMARY}>
			{children}
		</UiButton>

		<UiInput
			kind={EInputKind.PRIMARY}
			placeholder={placeholder}
			full-width
			className="mb-md"
			heading={heading}
			sub-label={subLabel}
		/>
	</div>
);

Flow to develop

  • We use only the develop branch as a base for creating new branches
  • Ensure to pull the latest changes before creating a new branch
  • Preferred naming of branches:
    • feature/[feature-name]
    • hotfix/[fix-name]
  • Preferred commit message
    • update([file[s]-name]): [message] for example - update(main.css, header.tsx): change header to .header
    • fix([file[s]-name]): [message]
    • add([file[s]-name]): [message
  • When you are ready to push just merge (do not rebase) develop into the current branch
  • Fix any merge conflicts that this creates
  • Next create pull request to develop (you can squash multiple commits when merging)
  • After the pull request is merged to develop you can see it in staging https://bonkers-ie.github.io/bonkers-ui
  • Only after reviewing and testing the changes in staging, then create a merge request from develop to master
  • After you merge to master, the patch version will upgrade x.x.^x and you can use this version in the package