Skip to content

Monorepo? #681

Closed
Closed

Description

@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

Activity

  1. self-assigned this
    on Mar 15, 2026
  2. added theissue type on Mar 15, 2026
  3. ovflowd commented on Mar 18, 2026

    @ovflowd
    Member

    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)

  4. avivkeller commented on Mar 18, 2026

    @avivkeller
    MemberAuthor

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

    import(specifier)?

  5. ovflowd commented on Mar 18, 2026

    @ovflowd
    Member

    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...

  6. avivkeller commented on Mar 18, 2026

    @avivkeller
    MemberAuthor

    I'll begin investigating once my current PRs here land

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions