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 can't find packages that don't exist when all packages are in the latest version #34

Open
ssccchh opened this issue Jun 27, 2022 · 1 comment

Comments

@ssccchh
Copy link

ssccchh commented Jun 27, 2022

// package.json
devDependencies: {
  "@vueuse/nuxt": "^8.7.4",
  "testpackage": "0.0.1"
}

// terminal
taze major
› - 1 patch

@vueuse/nuxt  dev  ~9d  ^8.7.4  →  ^8.7.5  ~5d

ERROR

> testpackage not found

Run taze -w to write package.json

taze -w
› - 1 patch

@vueuse/nuxt  dev  ~9d  ^8.7.4  →  ^8.7.5  ~5d

ERROR

> testpackage not found

ℹ changes wrote to package.json, run npm i to install updates.


taze major
dependencies are already up-to-date

When I run taze -w to update the versions of all packages in the package, and run taze major again, taze can no longer find the non-existent test package I wrote in the package.

@yuler
Copy link
Contributor

yuler commented Sep 4, 2022

I test this example

{
	"name": "xxx",
	"private": true,
	"devDependencies": {
		"@vueuse/nuxt": "^8.7.4",
		"testpackage": "0.0.1"
	}
}

Get the correct output

xxx - 2 major

  @vueuse/nuxt  dev  ~3mo  ^8.7.4  →  ^9.1.1  ~12d
  testpackage   dev         0.0.1  →   1.0.0  ~10y


Add -w to write package.json

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

2 participants