Skip to content

decision(storage-resize-images): kit/extension parity – CLI-installed kit runs Node 24, extension runs Node 22 #3328

Closed

Description

@CorieW

storage-resize-images kit/extension parity. Priority: low. Kits installed through the CLI run on a different Node.js major than the extension.

Difference

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

Reproduced

Seen in the CLI's generated wrapper. Not checked on the deployed function.

Code

Resolution

Accept it: the runtime follows the host codebase. Record it under "Decisions" in #3263.

Activity

  1. self-assigned this
    on Nov 10, 2026
  2. CorieW commented on Nov 10, 2026

    @CorieW
    MemberAuthor

    Decision: accept it. The runtime follows the host codebase, so CLI installs run Node 24 where the extension ran nodejs22. Recorded under "Decisions" in #3263.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

decisionNeeds a decision before work can proceedkitsparity

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions