Use meta to help manage the multi-repo dependencies #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does meta do
Gives you a convenient way to pull, sync, run commands across repos. Submodules are great but I guess clunky? meta does an okay job trying to solve this.
Screen.Recording.2025-12-08.at.5.20.04.PM.mov
Screen.Recording.2025-12-08.at.5.22.59.PM.mov
Changes
Multi-repo setup with meta
.metaconfig to clone dependent repos intorepos/subdirectoryrepos/to.gitignoreso cloned repos stay local.mprocs.yamlpaths from../torepos/for self-contained structureposthog/posthogorposthog/examplealready pulled and have separate changes there, this lets you avoid them.New npm scripts
pnpm setup:allpnpm pullpnpm statusmeta -- git statuspnpm wizard <cmd>pnpm posthog <cmd>pnpm examples <cmd>Other
metaas devDependency (v2.2.25).env.examplewith new repo pathspackageManagerfield for consistent pnpm versionUsage