Skip to content

m4bwav/package-modernize

v1.0.0MIT

Modernize an old published library end to end and release it again safely: survey, a golden capture of the published behaviour, a decisions-table plan that stops for the maintainer, a tested rewrite, an independent review, repository cleanup, a release rehearsal through trusted publishing with a human approval, registry verification and a handoff. npm and NuGet complete; PyPI, crates.io, Maven and Go documented and unverified. Nothing is published without the maintainer's approval. Evergreen.

GitHubOpen Website
package-modernize

Modernize an old published library end to end and release it again safely: an npm, NuGet, PyPI, crates.io, Maven or Go package moved to current tooling (TypeScript or ESM, CI). Eight phases: survey, golden capture of the published behaviour, a decisions-table plan that stops for the maintainer, a tested rewrite, independent review, repository cleanup (dead webhooks, stale bot pull requests, issues, leaked tokens), an approved release rehearsal, registry verification and a handoff. npm and NuGet complete, others unverified. Use whenever the user asks to modernize, revive, rewrite, re-release or update an abandoned or years-old package, wants trusted publishing or a safe release set up, asks for a modernization plan, survey or decisions table, or says 'the next package', 'run the playbook', 'modernize my NuGet library', 'update my old npm package'. Also for 'refresh package-modernize' and 'is package-modernize stale'. Not for app features, a one-off publish, or dependency bumps alone.