Have you considered a monorepo?
- Dominant language
- JavaScript
- Stars
- 1.6k
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Just came by your library through a chance. The functionality looks great. I started to wonder, though, if it would make sense to port it to monorepo style. You would end up with `@crocks/combinators` and so on. Note that npm made organizations free for open source projects a while ago and you can find tools like [Lerna](https://lernajs.io/) for managing the scheme.
The added benefit would be that this would allow you to split up the current README into something more focused per package. The main README of the project would give an overview of what the library is about and give your documentation some abstraction. You can also aggregate all this as a neat documentation site quite easily.
I wrote [a little blog post](https://medium.com/@bebraw/the-case-for-monorepos-907c1361708a) if you want to learn more about the approach.
Keep up good work. 👍
PS. Let me know if you want to do a little interview for the SurviveJS blog. I've been highlighting gems like this there every once in a while. 😄
Contributor guide
Assessment
This issue has not been assessed yet.