Add unstyled packages

[IzumiSy]

This PR adds a new component registry that contains unstyled components for Fabrix.

Currently, fabrix has only one component package (chakra-ui), but that's a bit confusing to see how fabrix itself work without UIs. Introducing unstyled components would be more helpful to see the behaviour without component concerns.

Purpose of the changes

• I am planning to add some working examples on docs that can be switched between styled and unstyled components to see that our package is pluggable in the frontend.
• As regads to demo purpose, I am observing that using UI component library on Stackblitz causes unavoidable wait in its up-time (almost 3-5 secs) when I use Vite because of bundling the package. That does not happen when I don't use any third-party UI packges, so I would like use unstyled package for our demo on Stackblitz as well for better experience.
• Unstyled package can be a good example to know what's needed in creating custom component registry.

Screenshot

[changeset-bot]

🦋 Changeset detected

Latest commit: 46d44ea

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@fabrix-framework/unstyled	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/fabrix-framework/fabrix/@fabrix-framework/chakra-ui@157

npm i https://pkg.pr.new/fabrix-framework/fabrix/@fabrix-framework/fabrix@157

npm i https://pkg.pr.new/fabrix-framework/fabrix/@fabrix-framework/unstyled@157

npm i https://pkg.pr.new/fabrix-framework/fabrix/@fabrix-framework/graphql-config@157

commit: 46d44ea

[toiroakr]

I think there was also an option to set as default fallback, but is there a specific reason you chose to publish as package instead?

[IzumiSy]

@toiroakr

I think there was also an option to set as default fallback, but is there a specific reason you chose to publish as package instead?

Actually, we don't have any default fallback now, so we can make this package the one for fallback in that sense.

And, the reasons why I added this package as the separated one are:

• I expect unstyled pacakage to be a good example to start creating custom components. To know fully about the dependencies and strcuture without distraction, I would like to make this package explicit and independent. If unstyled package is a part of the core package, that is a bit too complex to grasp the main concern to start creating the component registry from scratch.

  • Uniforms also takes the same approach that its guide says copy-paste the source code from their unstyled package (https://github.com/vazco/uniforms/tree/master/packages/uniforms-unstyled)

• Unstyled package is expected to be used as the demonstration purpose. The application in the real world would not use unstyled package, but it will use the hand-crafted custom components or other built-in packages like fabrix-framework/chakra-ui instead.