buidl
is a Web3 component library built using TailwindCSS and Radix for the TurboETH Web3 Build System.
The buidl
component library is being designed to compliment TurboETH which utilizes shadcn UI component library, TailwindCSS and Radix.
What makes buidl
unique?
A strong focus on a full-stack Web3 application.
Today many Web3 component libraries strictly focus on wallet connections and smart contracts interactions.
buidl
will of course include these essential components, but a strong emphasis will also be given to verifiable credentials, decentralized identity, identifier registries, distributed storage (Arweave, IPFS, etc...) and other core Web3 primitives.
Identity
-
<InputAccount />
-
<CredentialCardSmall />
-
<CredentialCard />
-
<CredentialCardLarge />
-
<CredentialCollection />
-
<FormCredentialIssue />
-
<IdentityCard />
-
<IdentityCardHorizontal />
-
<IdentityLinkages />
-
<VerifiablePresentationRequest />
Tokens
-
<InputToken />
-
<InputTokenAdvanced />
-
<FormTokenTransfer />
-
<FormTokenSwap />
DTS scaffolds your new library inside /src
, and also sets up a Vite-based playground for it inside /example
.
The recommended workflow is to run DTS in one terminal:
npm start # or yarn start
This builds to /dist
and runs the project in watch mode so any edits you save inside src
causes a rebuild to /dist
.
Then run either Storybook or the example playground:
Run inside another terminal:
yarn storybook
This loads the stories from ./stories
.
NOTE: Stories should reference the components as if using the library, similar to the example playground. This means importing from the root project directory. This has been aliased in the tsconfig and the storybook webpack config as a helper.
Then run the example inside another:
cd example
npm i # or yarn to install dependencies
npm start # or yarn start
The default example imports and live reloads whatever is in /dist
, so if you are seeing an out of date component, make sure DTS is running in watch mode like we recommend above.
To do a one-off build, use npm run build
or yarn build
.
To run tests, use npm test
or yarn test
.
Code quality is set up for you with prettier
, husky
, and lint-staged
. Adjust the respective fields in package.json
accordingly.
Jest tests are set up to run with npm test
or yarn test
.
Calculates the real cost of your library using size-limit with npm run size
and visulize it with npm run analyze
.
This is the folder structure we set up for you:
/example
index.html
index.tsx # test your component here in a demo app
package.json
tsconfig.json
/src
index.tsx # EDIT THIS
/test
index.test.tsx # EDIT THIS
/stories
Thing.stories.tsx # EDIT THIS
/.storybook
main.js
preview.js
.gitignore
package.json
README.md # EDIT THIS
tsconfig.json
We do not set up react-testing-library
for you yet, we welcome contributions and documentation on this.
DTS uses Rollup as a bundler and generates multiple rollup configs for various module formats and build settings. See Optimizations for details.
tsconfig.json
is set up to interpret dom
and esnext
types, as well as react
for jsx
. Adjust according to your needs.
Two actions are added by default:
main
which installs deps w/ cache, lints, tests, and builds on all pushes against a Node and OS matrixsize
which comments cost comparison of your library on every pull request using size-limit
Please see the main dts
optimizations docs. In particular, know that you can take advantage of development-only optimizations:
// ./types/index.d.ts
declare var __DEV__: boolean;
// inside your code...
if (__DEV__) {
console.log('foo');
}
You can also choose to install and use invariant and warning functions.
CJS, ESModules, and UMD module formats are supported.
The appropriate paths are configured in package.json
and dist/index.js
accordingly. Please report if any issues are found.