Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to a monorepo folder architecture and migrate to yarn3 #2786

Closed
charlesBochet opened this issue Dec 1, 2023 · 0 comments · Fixed by #2909
Closed

Migrate to a monorepo folder architecture and migrate to yarn3 #2786

charlesBochet opened this issue Dec 1, 2023 · 0 comments · Fixed by #2909
Labels
scope: back+front Issues requiring full-stack knowledge size: short type: chore

Comments

@charlesBochet
Copy link
Member

Scope & Context

We want to migrate to a monorepo folder architecture where all projects will be hosted under ./packages folder:

  • front, server and docs will move within ./packages folder

We will also switch to yarn3 which should optimize docker sizes (related to #965 and other investigations).

Once done, this should allow us a smoother interaction between sub-projects (especially twenty-ui, twenty-eslint and twenty-front and twenty-docs)

We will also aim to switch to vite if the performance is better (#2775)

Technical inputs

Example from our Medusa friends: https://github.com/medusajs/medusa

Feel free to chime in if you have advices on the best way to do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: back+front Issues requiring full-stack knowledge size: short type: chore
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant