fix(devkit): support pnpm catalogs

[HaasStefan]

Current Behavior

nx generate plugin throws the following error if a package like typescript is using the PNPM catalog feature in the package.json:

NX The package.json lists a version of typescript that Nx is unable to validate - (catalog:my-catalog)

"typescript": "catalog:my-catalog",

This is due too the semver validation that fails with the catalog.

Expected Behavior

If I am using a pnpm catalog, the package dependency should not be checked for a valid semver.

Related Issue(s)

Fixes #30035

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Feb 14, 2025 10:08am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 608a369.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	38m 16s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	18s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check --base= --he...	✅ Succeeded	12s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	10s	View ↗
nx documentation	✅ Succeeded	2m 31s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-14 10:51:10 UTC

[AgentEnder]

This util is used to get version numbers which are later used with semver helper methods, see:

nx/packages/angular/src/generators/setup-tailwind/lib/detect-tailwind-installed-version.ts

Lines 16 to 21 in 2d19500

	const version = checkAndCleanWithSemver('tailwindcss', tailwindVersion);
	if (lt(version, '2.0.0')) {
	throw new Error(
	`The Tailwind CSS version "${tailwindVersion}" is not supported. Please upgrade to v2.0.0 or higher.`
	);
	}

As such, we can't really just return the version with the catalog: protocol still there as that would result in downstream code failing as its expecting a semver.

I think to truly fix the issue you are seeing we'd need to be able to resolve the version, but I also don't love putting custom code in here for parsing pnpm-workspace.yaml and such.

[HaasStefan]

@AgentEnder, what are you suggesting? Would using a parser to retrieve the pnpm version number be alright if it is not colocated in this file?