build: prepare monorepo

[castarco]

Reorganise the code so the package @beautiful-tree/react is not at the root level of the repository, and we can have other packages as well.

Ideally, it should be done in a way that changes in a package only trigger the CI flow associated to that code and anything that depends on it, but nothing else (so we don't slow down our CI pipelines with useless work). Some tools that could help are Turbo Repo, or Nx.

This one is a precondition for the following tasks:

• feat: add Vue package #27
• feat: add Solidjs package #28
• feat: add "native" Web Component package #29
• feat: add Svelte package #30
• feat: add preact package #31

[bhishekprajapati]

Hey! I'm interested in contributing to create the vue version of beautiful tree. How can I get started?

[castarco]

Hi @bhishekprajapati 😄 ,

If you feel brave enough to pick the monorepo task first (as it's kind of a precondition), you can start with it. If you don't feel comfortable with the monorepo task, I can prioritise it on my side, so you can start with Vue after we have it in place (As I was working on it alone, I wasn't prioritising it yet).

NOTE: you can pick any task and leave a message so we can know that you are on it.

My suggestion is to start with the ones marked as "good first issue", but of course feel free to pick something else if you have any other preference.

Once you have your changes, you can send them as a PR and I'll review them.

[bhishekprajapati]

Hi @castarco ,
I've zero experience of monorepos.
I'll pick the vue task!

[bhishekprajapati]

Hey @castarco, do you any discord server or slack?
It'll be easier to discuss approaches!

[castarco]

Hi @bhishekprajapati , I'm sorry for the delay, I'm having a busy week. For the time being, there are no "real time" channels, but I'll prepare something this weekend 👍🏻 .

[bhishekprajapati]

@castarco
Sure!
Also, I saw the implementation. You did it using just svg.
I'm thing about implementing using html canvas.
What do you say?

[castarco]

Hi @bhishekprajapati .

1. I just created a "community" in Discord: https://discord.gg/dTapKEPEQe .
2. we can move all the async generic conversations to the Discussions section of this project 😃 .
3. I'm fine with an HTML Canvas implementation 😄 , I actually thought about that, but didn't want to put too much work on my shoulders. What I would do, though, is name it accordingly, so we have space for a "classic" SVG implementation as well. I'm thinking about something like @beautiful-tree/vue-canvas (feel free to explore other naming possibilities).

[castarco]

Going back to the main topic of this issue, I started working on it.