Does Deno not support a combined package/workspace?

[whalderman]

I'm trying to publish a package that is also a workspace, but Deno keeps giving me a error[excluded-module]: module in package's module graph was excluded from publishing error for all **/mod.ts files, even though they aren't excluded anywhere. The only files that are excluded are *.test.ts files.

The workspace's deno.json contains both "exports" and "workspace" -- does the "workspace" option disable the ability to publish the workspace as a package?

The error is throwing me off, mainly because it isn't even true (as far as I can tell from my deno.jsonc configs). If each approach ("exports"/"workspace") is mutually exclusive, that's fine.

[marvinhagemeister]

Not sure what's going on without further details. The workspaces and exports key are not mutually exclusive. The fresh repo uses a similar construct like you are describing here.

[whalderman]

Apologies for the lack of details, but thank you for the heads up regarding the fresh repo. I'll reference that to see what I'm messing up. 🙇‍♂️

[whalderman]

Hmm, I still can't determine what the root cause is. Even removing all "exclude" options in all deno.jsonc files still resulted in error[excluded-module] somehow. This is the repo if you're curious.

It's possible I'm missing something simple, but I have absolutely no idea why error[excluded-module] is so persistent. It only goes away when I remove the "workspace" property in the root deno.jsonc.

[marvinhagemeister]

Thanks for sharing more information. That does look indeed a bit cursed. Would you mind opening an issue for that https://github.com/denoland/deno/issues ?