Skip to content

[Spike] Evaluate fixture publication formats for downstream consumers #71

Description

@knytcomics-ui

Category

Spike

Question

Should fixtures be distributed as Git tags, release archives, an npm package, or a dedicated versioned data package?

Context

The package is private, consumers clone tags, and the adapter manually vendors JSON plus generated modules.

Why This Matters

The choice affects reproducibility, integrity, bundling, and synchronization.

Areas to Investigate

Git releases, npm JSON exports, standalone data packages, content-addressed artifacts, generated modules, and browser compatibility.

Evaluation Criteria

Reproducibility, verification, ergonomics, breaking changes, bundle impact, and maintenance cost.

Expected Deliverables

Comparison matrix, at least two small prototypes, recommendation, migration plan, and risks.

Acceptance Criteria

  • At least three approaches are compared.
  • Consumer installation and verification are demonstrated.
  • Versioning and rollback implications are documented.
  • Rejected alternatives are explained.

Follow-Up Opportunities

May inform immutable archives and compatibility tooling.

Cross-Repository Impact

Testkit, adapter, and research.

Complexity

Spike

Impact

High — determines the shared data delivery model.

Suggested Labels

spike, area: release, area: cross-repo

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