Support private workspace members in deno publish

[0x009922]

Use case

I have a Deno workspace, with some members being not intended for publishing. They serve more as a helper to organize the workspace. Specifically, some of them only define tasks in their deno.json and nothing else.

When I run deno publish, Deno complains that some workspace members do not have version field specified, and yes, it is on purpose.

Request

I would like to have something like the private: true field in package.json, which is respected e.g by PNPM & pnpm publish. Then, I can explicitly mark packages as private and deno publish should not take them into account.

Alternatively, it could be configured in the root deno.json's publish config. I tried to use publish.exclude, but it has a different purpose.