Skip to content

pnpm dlx resolve respecting minimumReleaseAge #10037

@dominikg

Description

@dominikg

Contribution

Describe the user story

When using pnpm dlx package-name it should fetch the latest version that matches minimumReleaseAge constraint in the global user config.

Describe the solution you'd like

  • get latest (or requested) tag version
  • if that satisfies minimumReleaseAge, use it
  • if not, go back to the previous patch/minor/major releases until you find one that does
  • error only if no version is found that satisfies minimumReleaseAge

Example:
latest: 2.1.0 released today
1.9.5 released 4 days ago
2.0.1 released 7 days ago

resolution should pick 2.0.1 here, not 1.9.5

Describe the drawbacks of your solution

resolution is more costly than just looking up one tag

Describe alternatives you've considered

User would have to manually list versions and explicitly pick one that satisfies the constraint

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions