@rdna/update
v0.2.0
Published
Inspect RDNA package registry provenance for update and eject workflows
Readme
@rdna/update
RDNA registry-provenance helper for non-destructive update and eject workflows.
It exposes importable metadata/update/eject plan APIs and the rdna-update CLI.
import {
createRdnaEjectPlan,
createRdnaUpdatePlan,
loadRdnaPackageMetadata,
scanRdnaApp,
} from "@rdna/update";
const entries = await loadRdnaPackageMetadata();
const updatePlan = await createRdnaUpdatePlan({ entries });
const ejectPlan = await createRdnaEjectPlan({ entries, components: ["Button"] });
const appReport = await scanRdnaApp({ cwd: "../target-app" });The CLI is non-destructive. Use rdna-update --check for a registry update plan
or rdna-update --eject Button for an eject plan.
Use rdna-update --cwd ../target-app --check to scan a target app without
writing files. Add --json for stable automation output:
rdna-update --cwd ../target-app --check --jsonThe app report includes RDNA package versions from package.json, RDNA import
files/specifiers, stale Next config workarounds, preview stubs, missing imported
RDNA dependencies, dna.config.json and app manifest presence, and
iframe/RadOS readiness findings such as X-Frame-Options: DENY blockers.
RadOS is an external consumer at https://github.com/Radiants-DAO/RadOS; this
package scans target app directories rather than a local DNA app workspace.
