David Sherret

deno compile should probably be storing relative paths instead of urls.

I think this is only ever useful if wildcards are supported? Or are you talking about npm workspaces? I think npm workspaces support negated patterns.

Ah ok, so basically you'd like: > Another nice feature might be to supports Cargo's semantics of excluding deno.json files that also declare their own workspace section. Currently, deno will...

> Another nice feature might be to supports Cargo's semantics of excluding deno.json files that also declare their own workspace section. Currently, deno will error out with a message stating...

Probably it should be documented here: https://docs.deno.com/runtime/manual/tools/unstable_flags/

Nope, not yet. This would be to add https://github.com/denoland/wasmbuild to the docs

Isn't this a formatting concern and not linting?

Yeah, this is essentially: https://github.com/dprint/dprint/issues/981#issuecomment-2889139693

Probably you're seeing it do a bunch of read dirs in directories that aren't specified on the command line? I'd rather have most of the matching go through the same...

I have a fix in #999 that will speed it up a bit based on my comment above, but there is a pending todo that would speed it up further....