Skip to content

chore(turbo): Move to a monorepo structure using turborepo - #73

Merged
JoseLion merged 3 commits into
mainfrom
chore/turbo-repo
Oct 25, 2022
Merged

JoseLion merged 3 commits into
mainfrom
chore/turbo-repo

Conversation

@JoseLion

Copy link
Copy Markdown
Contributor

This PR moves the structure of the repo to a mono repo using the popular turborepo library. This not only helps us to have the examples more organized but will also allow us to create separate packages, like plugins, within the same repository once the extension mechanism is ready. A few points to consider:

  • All the packages inherit from the same tsconfig.json base. Some require a few changes specific to their own use case.
  • The linter tool is at workspace level so we can lint the whole workspace
  • The main library of assertive-ts is now under packages/core
  • All new packages we include should go under the packages/ folder
  • All new examples we include should go under the examples/ folder

@Alex0jk Alex0jk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, I really like the new structure, but before approving I have two question:

  • Was this new structure auto-generated? Or was it manual?
  • I see there is a .mocharc file in the packages/core folders, is that expected there?

@JoseLion

Copy link
Copy Markdown
Contributor Author

@Alex0jk, thanks for reviewing the PR. Here are some answers to your questions:

Was this new structure auto-generated? Or was it manual?

  • It was manual. We can configure it in the way it best fits our needs

I see there is a .mocharc file in the packages/core folders, is that expected there?

  • Yes, each package works as a separate project in a mono repo, so we need to configure each tool were needed. There're some things we can share, like the tsconf.json in the root, but we still need a packages/core/tsconf.json which extends from the one in the root

Let me know if you want to talk more about these topics. Any feedback is welcome 🙂

@Alex0jk Alex0jk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the answers, the structure seems pretty good so I am approving this PR.

@JoseLion
JoseLion merged commit 479d3bc into main Oct 25, 2022
@JoseLion
JoseLion deleted the chore/turbo-repo branch October 25, 2022 21:04
@JoseLion JoseLion added the hacktoberfest-accepted PRs accepted during Hacktoberfest label Oct 25, 2022
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted PRs accepted during Hacktoberfest released

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants