Splitting core library into multiple libraries #6
Description
This looks great. I was wondering whether you’ve considered splitting the project into smaller, more focused libraries. Right now the main package pulls in quite a large number of dependencies, and as support for more systems grows, that list will only get bigger.
You could still offer a PipeFlowCore meta‑package that bundles everything for convenience, which would make it easy for newcomers to experiment. But for cases where I only need, say, Excel and SQL Server, it would be ideal not to bring in unrelated dependencies like MongoDB or AWS.
Just a thought — if it’s not something you want to tackle now, it might be worth considering for the future.