Wildcards being replaced (useful for monorepos)

[zomars]

Description

Monorepo packages that uses wildcard versions "example": "*" are being replaced by "example": "0.0.0"

Suggested Solution

Leave as it is?

Help Needed

Is there a way to prevent this? Couldn't find anything in the README about this.

[JamieMason]

It sounds like defining a semver group might be what you need, this would let you define which packages should only use *

https://github.com/JamieMason/syncpack#semvergroups

[zomars]

Tried adding this config but no luck still:

"semverGroups": [
      {
        "range": "*",
        "dependencies": ["@alpha/**"],
        "packages": ["**"]
      }
    ]

Still "@alpha/example": "*" is being transformed to "@alpha/example": "0.0.0"

[zomars]

Adding a custom filter works for now:

    "filter": "^(?!@alpha).*",

[JamieMason]

If you can share a reproduction I can take a look for you

[JamieMason]

Closing as blocked but please reopen with a repro if you find the time.

[JamieMason]

Actually, have a check with 8.3.9 – I found that support for setting versions to '*' wasn't available in any circumstances. All other ranges were supported.

[macieklad]

Hi, it seems that support for * is still broken with 8.3.9, i have created a simple repro, just run yarn syncpack and versions will be set to 0.0.0.

https://github.com/macieklad/syncpack-repro

[JamieMason]

I don't know what commands you guys are running (whether they're the version-related commands or the semver range commands) but looking at https://github.com/macieklad/syncpack-repro @macieklad I think the problem is that workspace is enabled by default, so it is using the versions of your own packages as the source of truth for what should be the correct version for them when they are used as a dependency.

If you set workspace: false in your /syncpack.config.js it should hopefully work as you're expecting. Give that a try @macieklad @zomars and I can try and help you from there if it does not get you what you need.

Thanks.

[macieklad]

That is a great clarification, I have missed that option entirely, thank you! The repo is working as intended now :> I think your answer will clarify it for others if they will stumble upon that again.

[JamieMason]

There is a new Getting Started guide now to help with some of these things.