💅 A theme-able library of reusable UI components
npm install @magiclabs/ui-components> A theme-able library containing reusable ui components
Current dev node version is 20.10
Please install node version manager nvm and use it to switch the node version
``bash`
cd /path/to/ui-components
nvm use
Follow NPM documentation to generate a token with access to private packages.
Next, you'll need to assign your NPM token to an environment variable in your preferred shell.
`zsh`
export NPM_TOKEN="00000000-0000-0000-0000-000000000000"
Refer to NPM's CI documentation for further information and troubleshooting help.
Go to https://figma.com, click your name in the top left corner, and go to settings. Scroll down to Personal access tokens and generate one with the default settings. Copy and enter it in the .env.local file for FIGMA_API_TOKEN.
Install NPM dependencies using PNPM:
`zsh`
pnpm install
| NPM Script | Description |
| ------------------------ | --------------------------------------------------------------------------------- |
| pnpm lib:dev | Start building the component library in development mode. |pnpm lib:build
| | Build the component library for production. |pnpm lib:publish
| | Cut a release for the current build |pnpm docs:dev
| | Start the Storybook environment in development mode. |pnpm docs:build
| | Build the Storybook environment for production. |pnpm test
| | Run local tests. |pnpm test:watch
| | Run local tests and watch for changes |pnpm test:ci
| | Run CI optimized tests. |pnpm test:tree-shaking
| | Test the component library for tree-shaking compatibility. |
1. Open a pull request from your fork/branch to the upstream master branch of _this_ repository.patch
2. Add a label for the semver update corresponding to your changes: , minor, or major.
3. A maintainer will review your code changes and offer feedback or suggestions if necessary. Once your changes are approved, a maintainer will merge the pull request for you and publish a release.
We use auto as our continuous delivery tool. Cutting a release is just a matter of merging to master. For pre-releases, you can create a next branch as the base for your experimental/W.I.P. feature. Please familiarize yourself with the documentation for auto if you are in a position to cut a release.
Integrating your app with Magic UI requires our client-side NPM package:
`zsh``Using PNPM:
pnpm add @magiclabs/ui-components