deno task --filter works only for submodules with "name" property in their deno.json

[AdiHarif]

Version: Deno 2.1.6

I tried to set up a monorepo with couple of deno modules and wanted to setup proper tasks with deno workspace.
Following this doc, when trying to invoke a submodule task using deno task --filter "client/*" dev or with any kind of variation of the package name i got the following error message - "No matching task or script 'dev' found in selected packages".

This got resolved for me when i have added a name property to the submodule's deno.json with the value "@scope/client".
Is this the behavior of requiring the name attribute in the submodule intended? if so, i would suggest updating the docs and maybe make the error message more informative.

In any case, would glad to contribute in that matter if my contribution is welcome :)
Thanks!

[bartlomieju]

Yes, this is an expected behavior. Any contributions to docs are very welcome :) you can edit this specific page here: https://github.com/denoland/docs/edit/main/runtime/reference/cli/task.md

[AdiHarif]

Thanks for the quick reply!

Follow up question - is the name property a strict requirement for submodules in general? should any operation expect this property exist in a submodule's deno.json?

[bartlomieju]

As a rule of thumb yes - a workspace member should have a name property - otherwise one can't refer to it between submodules.