You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bit is a tool for making components (both front- and back-end). Features:
easy set-up
good versioning and dependency support (component library currently uses lerna but not to full monorepo potential)
can grab components from different libraries
relatively easy deploy process
docs can include figma/designs
looks like good support for base components and other components build off them
does the back-end component thing mean we could use Bit for everything in the toolkit? Eg testing helpers, rjsf themes, etc.?
can use any stack
Cons:
slow to load new changes
users have to do additional setup to import components: npm config set @bit:registry https://node.bit.dev
doesn't reduce refactoring--we could bring in the components as is but the need for customization/flexibility means we're still going to need a component in every theme
The text was updated successfully, but these errors were encountered:
Bit is a tool for making components (both front- and back-end). Features:
Cons:
npm config set @bit:registry https://node.bit.dev
The text was updated successfully, but these errors were encountered: