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

@bioturing/components

v0.41.1

Published

BioTuring Design system React component library

Readme

@bioturing/components

A comprehensive UI component library for BioTuring applications built with React and Ant Design.

npm version License: CC BY-NC-ND 4.0

Installation

# Using npm
npm install @bioturing/components

# Using yarn
yarn add @bioturing/components

# Using pnpm
pnpm add @bioturing/components

Usage

import { Button } from '@bioturing/components';
import '@bioturing/components/style.css';

function App() {
  return (
    <Button type="primary">Hello BioTuring</Button>
  );
}

Available Components

The package provides the following components:

  • Badge
  • Breadcrumb
  • Button
  • Checkbox
  • CodeBlock
  • Collapse
  • DropdownMenu
  • Empty
  • Field
  • Form
  • Input
  • Popover
  • Radio
  • ScrollArea
  • Slider
  • Spin
  • Switch
  • Tag
  • Tooltip
  • Upload
  • VerticalCollapsiblePanel
  • And more...

Each component can be imported individually:

import { Button } from '@bioturing/components/Button';

Tree-Shaking Support

This package is fully optimized for tree-shaking, allowing you to import only the components you need:

✅ Recommended (Fully Tree-Shakable)

import { Button, Modal } from '@bioturing/components'
import '@bioturing/components/style.css'

Bundle Analysis

To analyze your bundle and verify tree-shaking effectiveness:

# Build the package
npm run build

# Open generated bundle analysis
open dist/stats.html

The component library uses:

  • ESM format for optimal tree-shaking
  • Preserved modules for granular chunking
  • Side-effects configuration for CSS handling
  • External dependencies to minimize bundle size

Modern bundlers (Vite, Webpack 5+, Next.js) will automatically eliminate unused components from your final bundle.

Styles

The package includes two CSS files:

// Main component styles
import '@bioturing/components/style.css';

// Tailwind utilities
import '@bioturing/components/tailwind.css';

Requirements

  • React 18.0.0 or higher
  • React DOM 18.0.0 or higher
  • Ant Design 5.24.9 or higher

Development Guidelines

ESLint Rules

This package enforces strict linting rules to ensure code quality:

  • No Console Statements: console.log() statements are not allowed in production builds.
    • In development, console statements will trigger warnings
    • In production, console statements will cause build errors
    • Only console.warn() and console.error() are permitted
    • The Vite build process automatically removes console statements in production

To run the linter:

# Check for linting issues
npm run lint

# Fix auto-fixable issues
npm run lint:fix

Documentation

For detailed documentation and examples, visit the BioTuring Design System documentation.

License

CC BY-NC-ND 4.0 © BioTuring