vendor/ — fork submodules (optional)

These are git submodules holding our forks of upstream projects. Nothing in the repo imports from vendor/ at runtime — code consumes the published packages from npm — so a fresh clone works without initializing submodules. They exist so the forks can be developed alongside the code that uses them.

Developing a fork

git submodule update --init vendor/mcporter
cd vendor/mcporter
pnpm install && pnpm build

To test local fork changes against the repo before publishing, point the consumer at the submodule build with a temporary file: override (or bun link), then revert once the new version is published:

// e2e/package.json (temporary, do not commit)
"@executor-js/mcporter": "file:../vendor/mcporter"

Releasing a fork

Bump the fork's package.json version, publish from the submodule (npm publish --access public), push the fork branch, bump the consumer's dependency here, and commit the new submodule pointer.