modular-library is a utility library for generating modular libraries.

Building a modular library manually is usually tedious and error-prone:

• keeping package.json exports in sync with your generated files,
• wiring and maintaining complex glob-based inputs,
• avoiding output path mistakes when your source tree grows.

modular-library is a zero-config way to generate modular outputs for vite, rollup, and rolldown with predictable structure.

A modular library is a library split into small, focused modules instead of one large, monolithic package.

This approach helps you:

• keep each part of the library easier to understand and maintain,
• reuse modules independently across projects,
• reduce coupling between features,
• improve scalability as the codebase grows,
• be tree-shakeable so consumers only bundle what they import,
• expose clear entry points for each public feature or component.

Typical examples of modular libraries include:

• UI libraries exposing per-component entries (for example @acme/ui/button, @acme/ui/modal),
• utility libraries exposing per-domain modules (for example @acme/utils/date, @acme/utils/string),
• SDKs exposing feature-based modules (for example @acme/sdk/auth, @acme/sdk/storage).

With modular-library, the goal is to make the creation of this kind of modular architecture faster and more consistent.

# Before (standard single-entry build)
dist/
  index.js

# After (modular output with modular-library)
dist/
  button.js
  modal.js
  utils/
    formatDate.js

Node.js requirement: This library supports only Node.js 22 or newer.

npm install modular-library

modular-library provides dedicated plugins for vite, rollup, and rolldown.

// vite.config.ts
import { defineConfig } from "vite";
import modularLibrary from "modular-library/vite";

export default defineConfig({
  plugins: [modularLibrary()],
  build: {
    lib: {
      entry: ["src/**/*.ts"],
      formats: ["es"],
    },
  },
});

// rollup.config.ts
import modularLibrary from "modular-library/rollup";

export default {
  input: ["src/**/*.ts"],
  output: {
    dir: "dist",
    format: "es",
  },
  plugins: [modularLibrary()],
};

// rolldown.config.ts
import modularLibrary from "modular-library/rolldown";

export default {
  input: ["src/**/*.ts"],
  output: {
    dir: "dist",
    format: "es",
  },
  plugins: [modularLibrary()],
};

All plugin variants support the same options:

Example with options:

import modularLibrary from "modular-library/rollup";

export default {
  input: ["src/**/*.ts"],
  output: {
    dir: "dist",
    format: "es",
  },
  plugins: [
    modularLibrary({
      relative: "src/",
      transformOutputPath: (outputPath) => `modules/${outputPath}`,
    }),
  ],
};

To make your package consumable with subpath imports, add an exports map in your package.json:

{
  "exports": {
    "./*": "./dist/*.js"
  }
}

You can also use modular-library as a CLI with npx.

Validate that all package.json export targets exist and are inside your output directory:

npx modular-library check

Named options:

• --package-json path to package manifest (default: ./package.json)
• --out-dir output directory to validate against (default: ./dist)

Example:

npx modular-library check --package-json ./package.json --out-dir ./dist

npm install
npm run build
npm test

To test GitHub workflows locally, you can use act.

ISC