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

support/configure allowing workspace:* #147

Closed
juliusmarminge opened this issue Oct 3, 2022 · 4 comments · Fixed by #204
Closed

support/configure allowing workspace:* #147

juliusmarminge opened this issue Oct 3, 2022 · 4 comments · Fixed by #204

Comments

@juliusmarminge
Copy link

Would it be possible to allow for workspace:* to be used as version?

I use this for internal packages that I don't publish in create-t3-turbo. It works on main that is using npm but in this PR where I'm migrating to PNPM manypkg fails with this error.

@butterybread
Copy link

I am running into this issue as well.

error <package-a> has a dependency on <package-b>@workspace:* but the version
of <package-b> in the repo is 0.0.1 which is not within range of the depended on version,
please update the dependency version

@ColdSauce
Copy link

Running into this issue as well.

Quick mitigation on my end to ignore these errors:

manypkg check |& grep -v '@workspace'

Unfortunately, color is lost.

@hmans
Copy link

hmans commented Oct 11, 2022

Unfortunately, color is lost.

Also, manypkg fix will still overwrite these fields. :(

@theKashey
Copy link

This story started long long time ago #72

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