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

Taze does not find updates #130

Open
5 of 7 tasks
kuddl opened this issue Jul 19, 2024 · 2 comments
Open
5 of 7 tasks

Taze does not find updates #130

kuddl opened this issue Jul 19, 2024 · 2 comments

Comments

@kuddl
Copy link

kuddl commented Jul 19, 2024

Describe the bug

I have a very simple project.
I did a fresh pnpm install.
I tried to use taze to update the dependencies.

It did not work.

  • nlx taze major did not show any updates
  • pnpm outdated did show updates
  • the npm-check-updates` also shows updates

See screenshot.
image

Reproduction

  • use this package.json
  • run npm i or pnpm i
  • run npx taze or with major or latest ; even with a globally installed version of taze
  • => does not show any updates
  • run pnpm outdated or npm outdated and it shows updates
{
  "name": "kuddl-dev",
  "private": true,
  "type": "module",
  "scripts": {
    "build": "nuxt build",
    "dev": "nuxt dev",
    "generate": "nuxt generate",
    "preview": "nuxt preview",
    "postinstall": "nuxt prepare"
  },
  "dependencies": {
    "nuxt": "3.11.2",
    "vue": "3.4.26",
    "vue-router": "4.3.2"
  },
  "prettier": "3.2.5",
  "prettier-plugin-tailwindcss": "0.5.13",
  "devDependencies": {
    "@nuxt/fonts": "0.6.1",
    "@nuxt/ui": "2.15.1",
    "tailwindcss": "3.4.3"
  }
}

System Info

System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1 Pro
    Memory: 160.67 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.version-fox/temp/1721340000-99154/nodejs/bin/node
    npm: 10.5.0 - ~/.version-fox/temp/1721340000-99154/nodejs/bin/npm
    pnpm: 9.5.0 - /opt/homebrew/bin/pnpm
    bun: 1.1.12 - ~/.bun/bin/bun
  Browsers:
    Chrome: 126.0.6478.183
    Edge: 126.0.2592.102
    Safari: 17.5

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.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
@antfu
Copy link
Member

antfu commented Jul 19, 2024

Have you tried taze -f? By default taze caches the metadata for half an hour or so

@mheob
Copy link

mheob commented Oct 14, 2024

It seems that the problem is that the version numbers are pinned and don't have a range.
I have the same problem in a repo where all dependencies are pinned.

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