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

can't find upgarde of some package #71

Open
5 tasks done
tjx666 opened this issue Jul 8, 2023 · 6 comments
Open
5 tasks done

can't find upgarde of some package #71

tjx666 opened this issue Jul 8, 2023 · 6 comments

Comments

@tjx666
Copy link

tjx666 commented Jul 8, 2023

Describe the bug

for example package: @yutengjing/tsconfig-node.
There is already version: v0.0.3, but taze can't find the upgarde.

Reproduction

https://stackblitz.com/edit/node-cyyrfx?file=package.json

System Info

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
    pnpm: 8.6.3 - /usr/local/bin/pnpm

Used Package Manager

pnpm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.
@jaw52
Copy link
Contributor

jaw52 commented Jul 18, 2023

pic
I used your demo and taze found a new version of the dependency package

@tjx666
Copy link
Author

tjx666 commented Jul 18, 2023

@rubiin
Copy link

rubiin commented Aug 15, 2023

+1

@jaw52
Copy link
Contributor

jaw52 commented Aug 24, 2023

This is probably not because of taze.

The reason can be seen here npm/node-semver#281

@jaw52
Copy link
Contributor

jaw52 commented Aug 24, 2023

@antfu Hi~,This issue is due to the design of node-semver. Maybe it can be closed
npm/node-semver#281

@jaw52
Copy link
Contributor

jaw52 commented Aug 24, 2023

@antfu Hi~,This issue is due to the design of node-semver. Maybe it can be closed npm/node-semver#281

Or does this require support for the default upgrade to ^0.0.x?

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

No branches or pull requests

3 participants