Monorepo?

[avivkeller]

What do we think about turning this repository into a monorepo? That way, consumers will only import things that are actually needed.

Then, -t (--target) would specify a package, i.e. -t @doc-kit/web or -t @doc-kit/legacy/html. Users can then extend existing generators with custom packages.

cc @nodejs/web-infra

[ovflowd]

I'm unsure how specifying generators with package-name would work, because we need to be able to resolve also local generators, so we would need to use some Node.js resolution mechanism so that it supports full node module coverage (absolute paths, relative, package name, etc)

[avivkeller]

I'm unsure how specifying generators with package-name would work, because we need to be able to resolve also local generators,

import(specifier)?

[ovflowd]

I'm unsure how specifying generators with package-name would work, because we need to be able to resolve also local generators,

import(specifier)?

🤷 needs to be a bit more safeguardy I'd say. To be clear, Im fine with it being a monorepo. We need this to be a monorepo if we want to achieve our 2026 goals #594 and if we want to allow non-Node.js teams to use it...

[avivkeller]

I'll begin investigating once my current PRs here land