refactor: converting from monolith to monorepo, starting package decomposition #535
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's been a while since we're talking about monorepos, so let's do it!
This PR is really just a first step. There's still quite a bit of work to modularize things further, but let's save that for future PRs.
Basically, in step 1, the romcal library is converted into a package within the monorepo
@romcal/rite-roman1969
. Later on, we can continue to refactor certain elements into different packages (for future PRs). I've already made a first one:@romcal/easter
(which contains the code to calculate the date of Easter).I think the key here is to stabilize the current configuration. I've continued to use
npm
to set up this monorepo. I'm more used to usingpnpm
thannpm
in monorepo projects, so I'd appreciate some help fine-tuning the configs and package.json withnpm
(for now, it's pretty basic).Here's the start of the new structure:
For now, everything remains functional in the same way, using the npm package
romcal
(to avoid breaking changes).If you'd like to contribute to this PR as well, feel free to do so 😉