Kevin Ingersoll

We currently won't see Docker build failures until things land in main, so we should probably do this as part of the CI build step so we can see them...

this was named 1) before we started using the "label" term in config, etc. and 2) not clearly enough to infer that this is for debugging/human-readability purposes, not meant to...

we need a table for resource labels (and likely for metadata in general) so that we can later hydrate a MUD config from these labels (when available)

rename resource labels in config output

1

rather than `label` everywhere, rename to `tableLabel`, `systemLabel`, `namespaceLabel` and also add `namespaceLabel` to each table and system output object

things like eslint, TS, arktype, tsx, etc. can all be moved to workspace root to avoid installing in multiple places and managing versions everywhere

they're currently hard to work with

https://github.com/latticexyz/mud/blob/ab985f29360328e30bc4aecb9985410a015bcc7b/packages/common/src/foundry/index.ts#L37-L39 we added `sourceDirectory` to MUD config in https://github.com/latticexyz/mud/pull/2840 and have since moved nearly everything to this option, just a few spots left to migrate related to https://github.com/latticexyz/mud/pull/2941

got this warning with `pnpm create mud` > WARN  deprecated [email protected]: Rimraf versions prior to v4 are no longer supported

In playing with manifests and generating metadata files from config + filesystem state, we found that we could maybe resolve some issues/complexity around TS by writing config output to a...