Skip to content

Decision: revive resume-cli in the monorepo, or formally deprecate? #785

@thomasdavis

Description

@thomasdavis

resume-cli is the project's #1 entry point (4,719★) but is effectively unmaintained: package.json pins engines: ">=12 <18" so it will not install on modern Node (18/20/22+), and the README states it is not actively maintained.

Decision needed (pick one):

  1. Revive inside the jsonresume.org monorepo as packages/cli — modernize to Node 20+, replace the legacy Puppeteer/Babel toolchain, reuse the registry's Playwright PDF rendering, and keep publishing the resume-cli npm name from the workspace (import history via git-filter-repo/subtree).
  2. Formally deprecate — pin a deprecation notice in the README, keep v3.1.2 published for backward compatibility, and redirect new users to the registry / Resumed.

Either way, stop it silently rotting at the front door. Part of the org consolidation audit: jsonresume.org#275.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions