Skip to content

enhancement: add Node.js and framework version selection (Express, Next.js, NestJS) #3

@marcosgdz03

Description

@marcosgdz03

Context

Node.js project generation supports:

  • Express
  • NestJS
  • Next.js :contentReference[oaicite:2]{index=2}

But currently:

  • No Node.js version selection
  • No framework version control

Goal

Add full version management for Node.js ecosystem during project creation.

Functional Requirements

  • Select:
    • Node.js version (16, 18, 20 LTS)
    • Framework (Express, Next.js, NestJS)
    • Framework version
  • Generate:
    • package.json with exact versions
  • Optional:
    • .nvmrc file
    • engines field in package.json

UX/UI

  • Extend existing QuickPick flow
  • Show LTS recommendations
  • Warn about incompatibilities (e.g., Next.js vs Node version)

Technical Considerations

  • Fetch versions from npm registry
  • Cache version metadata
  • Keep compatibility with current generator structure

Acceptance Criteria

  • Users can select Node.js + framework versions
  • package.json reflects selected versions
  • Project runs correctly after generation

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions