Skip to content

A blueprint for a component library with tree-shaking, TypeScript and a MonoRepo

License

Notifications You must be signed in to change notification settings

LukasBombach/tree-shakable-component-library

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Tree-shakable component library with TypeScript, StoryBook & Next.js

This repository is the demonstration of my dev.to article

👉 https://dev.to/lukasbombach/how-to-write-a-tree-shakable-component-library-4ied

demonstrating how to implement a tree-shakable component library (with TypeScript, StoryBook & Next.js all in a Monorepo).

For questions you can find me on twitter as @luke_schmuke

Install

git clone https://github.com/LukasBombach/tree-shakable-component-library
cd tree-shakable-component-library
yarn

Run

This MonoRepo has 2 packages

The app is a Next.js app that consumes the ui-library in the index.tsx page while the ui-library provides bundled components.

You can run the app by switching to the app folder and run yarn dev or yarn start*
* both packages have postinstall script that runs yarn build in each project

Run the app

cd packages/app
yarn dev

You can also run StoryBook from within the ui-library

Run StoryBook

cd packages/ui-library
yarn storybook

You can change or add new components by running

Develop new components

cd packages/ui-library
yarn build -w

in another terminal you can run the app in parallel and it will auto-update with hot-module-reloading

cd packages/app
yarn dev

See the tree-shaking

You can very simple see that the app actually does tree-shake your code by opening this project in a code editor and searching all files in packages/app/.next and

  1. searching for the string I SHOULD BE HERE, which should be found. This string is part of the Button component which has been loaded into the app
  2. then search for the string I MUST NOT BE HERE This string is part of the Link component which has not been loaded into the app even though it has been bundled in the ui library and should not be bundled in the app.
  3. check out the file packages/ui-library/lib/index.esm.js which is the bundled file of the ui-library which includes all components

About

A blueprint for a component library with tree-shaking, TypeScript and a MonoRepo

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published