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

@kaizen/package-bundler

v2.0.3

Published

Bundles libraries

Downloads

42,371

Readme

@kaizen/package-bundler

Bundle packages as CJS and ESM with TypeScript types.

ESM code is tree-shakeable.

pnpm add -D @kaizen/package-bundler

build-shared-ui

For shared UI packages. CSS modules and/or Tailwind will be included in the dist in a single stylesheet ({PACKAGE_NAME}/dist/styles.css) to be imported by the consumer.

Note: If your package extends another shared UI package, you will need to list the other package as a peerDependency and have the end consumer import both stylesheets.

package.json

Add the following to your package.json:

"main": "dist/cjs/index.cjs", // CommonJS entrypoint
"module": "dist/esm/index.mjs", // ES modules entrypoint
"types": "dist/types/index.d.ts", // TypeScript types entrypoint
"files": [
  "dist" // Ensure dist dir is included in package
],
"sideEffects": [
  "styles.css" // Ensure styles do not get tree-shaken
],
"scripts": {
  "build": "pnpm package-bundler build-shared-ui",
}

Dependencies

pnpm add -D postcss postcss-preset-env rollup tslib

devDependencies:

  • postcss
  • postcss-preset-env
  • rollup
  • tslib (peerDep of rollup)
  • If using Tailwind:
    • tailwindcss

Required files

  • postcss.config.js
  • rollup.config.mjs
  • tsconfig.json
  • tsconfig.dist.json
  • If using Tailwind:
    • tailwind.config.js
    • src/tailwind.css

PostCSS

In postcss.config.js:

module.exports = {
  plugins: {
    'postcss-import': {},
    'cssnano': {},
  },
}

If using Tailwind:

module.exports = {
  plugins: {
    'postcss-import': {},
    'tailwindcss/nesting': 'postcss-nesting',
    'tailwindcss': {},
    'autoprefixer': {},
    'cssnano': {},
  },
}

Rollup

In rollup.config.mjs:

import { pluginsSharedUi, rollupConfig } from '@kaizen/package-bundler'

export default rollupConfig({
  // Add extra entrypoints as required
  input: { index: './src/index.ts' },
  plugins: pluginsSharedUi,
})

tsconfig

// tsconfig.json
{
  "extends": "@kaizen/package-bundler/tsconfig.base.json"
}

// tsconfig.dist.json
{
  "extends": "./tsconfig.json"
}

Tailwind

pnpm add -D tailwind @kaizen/tailwind

Required files:

  • tailwind.config.js
  • src/tailwind.css

Follow the set up guide.

As we use PostCSS, ensure your postcss.config.js has the following plugins installed:

module.exports = {
  plugins: {
    'postcss-import': {},
    'tailwindcss/nesting': 'postcss-nesting',
    'tailwindcss': {},
    'autoprefixer': {},
    'cssnano': {},
  },
}

If you are creating a UI library to share with others, ensure you set a unique prefix to avoid clashes with other libraries.

// tailwind.config.js
module.exports = {
  prefix: '{uniquePrefix}-',
}

Alias

If you are using aliases, ensure you have them listed in your tsconfig.json (the tsconfig.dist should extend this).

Example:

// tsconfig.json
{
  "compilerOptions": {
    "paths": {
      "~components/*": ["./src/*"],
    }
  }
}

// tsconfig.dist.json
{
  "extends": "./tsconfig.json",
}