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

Convert to monorepo #29

Open
jorins opened this issue Dec 16, 2023 · 0 comments
Open

Convert to monorepo #29

jorins opened this issue Dec 16, 2023 · 0 comments
Labels
infrastructure Relating to the project's structure and CI/CD

Comments

@jorins
Copy link
Contributor

jorins commented Dec 16, 2023

Due to the complexity of maintaining multiple versions of documentation (#6), we have the need for developing tooling that would be best kept outside the main project. This is not unlikely to happen in other ways too, and working proactively with setting up a monorepo is probably a good idea.

Another potential use case already is setting up separate modules for node and web that the main module can re-export, but they can be tested individually under different circumstances with regards to available types and APIs.

A change to a monorepo structure would probably mean switching to pnpm, which should not cause any problems by itself. We shouldn't need tools like turbobuild from day one but I could be wrong.

@jorins jorins added the infrastructure Relating to the project's structure and CI/CD label Dec 16, 2023
@jorins jorins mentioned this issue Dec 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
infrastructure Relating to the project's structure and CI/CD
Projects
None yet
Development

No branches or pull requests

1 participant