Allow --ignore-path option with a path that is not exist in workspace

[yossiyedid]

I'm running
check-dependency-version-consistency --dep-type=dependencies --dep-type=peerDependencies --dep-type=devDependencies --ignore-path-pattern=dist",
On my local run, I have dist folders with package.json I want to avoid, and on CI they don't exist.

While they do not exist in CI, I get an error
Specified option '--ignore-path-pattern /dist/', but no matching paths were detected in the workspace.
And then it breaks the run.

I want to pass a pattern that won't break the run even if it's not in the workspace.

thanks

[bmish]

It's a good point that there may be paths you want to ignore locally but not in CI.

Right now, all of our options will throw an error when they are used unnecessarily. This helps catch mistaken or obsolete usage.

I'm open to reconsidering or tweaking this behavior. Ideally, we would follow whatever the best practices are for "ignore path/pattern" options like this. For example, we should investigate how related tools like ESLint handle this.

[AlonMiz]

In this case, it would make sense to show a warning instead of failing. Alternatively, introducing a --strict flag (defaulting to true) could be a good solution—this way, users can opt out of strict behavior if needed.

The issue with dist folders containing unwanted package.json files is quite common, especially in Angular projects and similar setups. Since these folders are not part of the actual source code, a more permissive behavior feels appropriate here.