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

Transition to Monorepo using Turborepo, PNPM, Changesets, and Vite #725

Closed
easylogic opened this issue Jan 12, 2024 · 1 comment
Closed

Comments

@easylogic
Copy link
Contributor

Description:
I propose to restructure the "yorkie-js-sdk" project into a monorepo. This transition will involve the integration of several modern tools to streamline our development process and enhance scalability. The key tools we plan to use include:

  • Turborepo: For efficient handling of multiple packages within the monorepo, ensuring faster builds and testing.
  • PNPM: As our package manager, offering better performance and disk space efficiency compared to traditional package managers.
  • Changesets: To manage and automate versioning and changelog generation, ensuring a smooth release process.
  • Vite: Leveraging its capabilities for rapid frontend development, enhancing our overall productivity.
    This restructuring aims to improve the manageability of our project, making it easier to scale and maintain.

Why:

  • Scalability: A monorepo approach will simplify scaling our project as it grows, making it easier to manage multiple interdependent components.
  • Efficiency: Using Turborepo and PNPM will significantly improve our build times and dependency management.
  • Release Management: With Changesets, we can automate and streamline our release process, enhancing consistency and reliability.
  • Developer Experience: Integrating Vite will offer a much faster and more enjoyable development experience, especially for our frontend components.

CheckList:

  • []
@easylogic easylogic mentioned this issue Feb 1, 2024
25 tasks
@hackerwins
Copy link
Member

Dup of #648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants