Affected Packages

Problem

When configuring a package as ignored by directly naming it, there are validation checks that lead to this error:

The package "packageA" depends on the ignored package "packageB", but "packageA" is not being ignored. Please add "PackageA" to the `ignore` option.

However, when configuring it with a wildcard, this error is no longer thrown.

I am unsure why this error was introduced exactly, however for my use case, I need to be able to ignore a package without getting this error. This is my use case:

I have a project with publishable packages, and a few private shared workspace packages that help define configurations for development purposes.

The advised way to skip these types of packages is to remove their version fields, however with pnpm, the version field is required when publishing.

This is an open issue here

Proposed solution

My suggestion is to remove the error completely and to update the docs to both document that wildcards are supported (this was documented), and to remove the disclaimer that suggests that this should be a temporarily set field.

Alternatively, we should update the validation logic to detect packages captured by wildcards so that we don't have an inconsistent experience and the use case should be expanded upon so that it is clear why this error exists. If this is the option chosen, then we should also discuss the use case I gave above to find an alternative solution for it.