I can't stress enough just how incredibly useful and well-crafted @deepkit/type and @deepkit/type-compiler are. Personally, I would even go as far as to say that I'd like to see them integrated in Node/Deno/Bun one day.
Given that they are already independent of every other component of the DeepKit framework, could it make sense to move them to a dedicated repository? Based on my direct experience, doing so might help with bringing others to help out with maintenance. For example, I'm planning to have a go at #698 and #699 in the near future but I'm a little hesitant to set up the entirety of the framework, which includes things like libpq5 and libpq-dev as per DEVELOPMENT.md.
Obviously I completely understand the advantages of keeping everything in a monorepo and I'm not arguing - at all - for separating all packages out into dedicated repositories. However, @deepkit/type feels to me to be of such universal value that having it live in its own repo might make for a reasonable tradeoff.
I can't stress enough just how incredibly useful and well-crafted
@deepkit/typeand@deepkit/type-compilerare. Personally, I would even go as far as to say that I'd like to see them integrated in Node/Deno/Bun one day.Given that they are already independent of every other component of the DeepKit framework, could it make sense to move them to a dedicated repository? Based on my direct experience, doing so might help with bringing others to help out with maintenance. For example, I'm planning to have a go at #698 and #699 in the near future but I'm a little hesitant to set up the entirety of the framework, which includes things like
libpq5andlibpq-devas perDEVELOPMENT.md.Obviously I completely understand the advantages of keeping everything in a monorepo and I'm not arguing - at all - for separating all packages out into dedicated repositories. However,
@deepkit/typefeels to me to be of such universal value that having it live in its own repo might make for a reasonable tradeoff.