Skip to content

feat: public plugin/template API + valibot/Standard Schema validator option #193

Description

@benjamineckstein

Batch D · Priority P2 · strategic

No public extension point. There is an internal plugins/ folder but no documented plugin registration, template overrides, post-generation hooks, or naming-strategy override. The exported generate* functions imply an API that isn't documented or stable. hey-api ("20+ plugins"), kubb ("meta framework"), and orval (output hooks) all offer this; without it, any team hitting an edge must fork — an adoption cliff beyond greenfield.

Pair with a valibot / Standard Schema validator option (hey-api ships valibot; valibot's tree-shaking is directly on-brand for a "zero-footprint" project; Standard Schema is the emerging abstraction to target).

Effort: L (plugin API), M (valibot path).

Source: Opus competitive analysis, gaps G3 + G7; product review C5.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions