decision(delete-user-data): kit/extension parity – CLI-installed kit runs Node 24, extension runs Node 22 #3261

delete-user-data kit/extension parity. Priority: low. Kits installed through the CLI run on a different Node.js major than the extension.

Difference

• Extension: every function runs nodejs22.
• Kit: firebase functions:kits:install and ext:migrate generate a wrapper package.json with "engines": { "node": "24" } (the CLI's latest runtime), so the functions deploy on nodejs24. The kit itself declares >=22. With the README's manual setup, the runtime is whatever the user's own codebase uses.

Reproduced

After ext:migrate, the kit's clearData, handleSearch and handleDeletion reported buildConfig.runtime: nodejs24. The source extension instance reported nodejs22. Deletion behaviour was the same in testing.

Code

• Extension: extension.yaml#L67, #L75, #L83.
• Kit: package.json#L23-L25; the wrapper's runtime comes from firebase-tools' package-kit.json template.

Resolution

Two options:

• Accept this and record it as an accepted difference under "Decisions" in delete-user-data kit tracking issue #3249 (it applies to every kit).
• Have ext:migrate keep the extension's runtime when it generates the wrapper.