Open
Conversation
Contributor
|
@jsj is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
emulate already uses a plugin-shaped internal architecture through per-service packages and ServicePlugin, but new emulators still require hardcoded core registry changes. This change reuses that existing service-entry path to allow external plugins while preserving built-in behavior and keeping scope limited to loading, listing, init, and programmatic startup.
…tection Preserve ServiceName autocomplete with branded string pattern, load plugins in parallel, and guard against name collisions with built-in services or duplicate plugins.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0d21292529
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Adds a
--pluginflag to load external emulator services at runtime without modifying the core package.start,init, andlistcommands, and the programmaticcreateEmulatorAPIMotivation
The service list is growing steadily (#38 Clerk, #47 Stripe, #51 Resend) and each addition is a PR into core. This works today, but the trajectory points toward a repo that gets heavier with every service while many use cases — internal APIs, niche platform emulators, org-specific services — will never belong upstream.
The
@emulators/*packages already follow a plugin-shaped contract internally. This PR exposes that contract so external consumers can load their own services the same way:No fork required, no upstream PR needed for services that only matter to one team.
Longer term this opens the door to a Vercel Skills-style architecture: a thin core runtime with a community gallery of service plugins, where built-in services are just the default set rather than the only option.
Plugin contract
A plugin module exports:
plugin(or default export) — aServicePluginwithnameandregister(app)seedFromConfig,label,endpoints,defaultFallback,initConfigTest plan
createEmulatorAPIinitCommandgenerates config for an external plugin