Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unmatching engines on Glob library update #2785

Closed
2 of 4 tasks
jirp-upc opened this issue Nov 4, 2024 · 3 comments
Closed
2 of 4 tasks

Unmatching engines on Glob library update #2785

jirp-upc opened this issue Nov 4, 2024 · 3 comments

Comments

@jirp-upc
Copy link

jirp-upc commented Nov 4, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

Glob 11.0.0 specifies those engines:

"engines": { "node": "20 || >=22" },

while this repository specifies:

"engines": { "node": ">= 16.14" },

This update was made from this commit: https://github.com/nestjs/nest-cli/commit/fc6e7a166f94389a5a0378d275ef5e3b86ed7bc5

Minimum reproduction code

fc6e7a1

Steps to reproduce

pnpm i

Expected behavior

Use a glob version that matches engines specification of this repository

Package version

10.4.6

NestJS version

No response

Node.js version

18.17.1

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

No response

@kamilmysliwiec
Copy link
Member

#2786

@dnln
Copy link

dnln commented Jan 21, 2025

@kamilmysliwiec I'm seeing this issue with 11.0.1 which looks to have been released to npm a few hours ago.

Locally I've pinned the version to 10.4.9 which resolves the issue, but this bug seems to have been reintroduced.

@kamilmysliwiec
Copy link
Member

@dnln

Image

Nest CLI v11 requires Node v20

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

No branches or pull requests

3 participants