Trying to publish a non-existent package gives a confusing message

[i-e-b]

Found when running a 'version remapper' through

    return workspace.workspacePackages({ additionalPaths: [ "./node_modules" ] })
        .pipe(workspace.filter(function (packageDescriptor, packagePath) {
            return packageDescriptor.name.startsWith(PACKAGE_PREFIX);
        }))
        .pipe(versionReMapper);

And the workspace packages contain references to a deleted package.

This results in the error message "Circular dependency found in Workspace: ..."
Coming from WorkspacePackages.ts::streamPackages (around line 135).

Looks like any failure in the callback is assumed to be a circular dependency.

Idea: Run the findPackageNames function, and only give the circular dependency message if there is a match. Otherwise give a generic message including the target file name.