feat: add support nx@^15.0.0 in config-nx-scopes

[Phault]

Expected Behavior

Using config-nx-scopes should be compatible with Nx 15, without installing with --legacy-peer-deps flag.

Current Behavior

Usage with Nx 15 requires using npm install --legacy-peer-deps, but otherwise works fine.

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

Update the Nx version range in package.json to nx: "^14.0.0 || ^15.0.0" in peerDeps

Context

No response

[trystan2k]

Hi @escapedcat ,

I have just publish a PR to solve this.

Instead of update version as proposed in this issue nx: "^14.0.0 || ^15.0.0", I have just left the latest version nx: ^15.0.0.

Let me know if I need to change it to the || option.

[escapedcat]

I guess that would a breaking change then, right? Woudl be ok I guess.

[trystan2k]

I guess that would a breaking change then, right? Woudl be ok I guess.

Yep, that would be a breaking change. But I guess that if someone jump from a major release of NX (from 14.x to 15.x), it should also mean a major update for other dependencies too.

[Phault]

I see no reason to drop support for Nx 14 until config-nx-scopes actually requires some newer Nx feature.

[escapedcat]

Fair enough

[trystan2k]

Should I then change the peerDependency to nx: "^14.0.0 || ^15.0.0" ? (and keep the devDependency to 14.0.0 or no problem to update to 15.0.0 ?)

[escapedcat]

@Phault is right, as long as there is no need for a breaking change, let's avoid it and just make sure v15 is supported.
Thanks everyone!

[Phault]

Yeah I think so. Keep devDep as-is so we don't accidentally start relying on a Nx 15 feature without realizing it.

[trystan2k]

@escapedcat @Phault Ok ! Agree ! I have reverted changes and just added the 15.0.0 as peerDependency (together with 14.0.0).
Thanks !

[escapedcat]

Thanks! Creating a release now.