Skip to content

[world] Add various @fantasticfour org worlds to manifest#1964

Merged
pranaygp merged 1 commit into
vercel:mainfrom
vinnymac:vt/ff-worlds
May 14, 2026
Merged

[world] Add various @fantasticfour org worlds to manifest#1964
pranaygp merged 1 commit into
vercel:mainfrom
vinnymac:vt/ff-worlds

Conversation

@vinnymac
Copy link
Copy Markdown
Contributor

@vinnymac vinnymac commented May 9, 2026

Let me know if you'd prefer if I tweak the changes here, as I have never submitted a community world before. The world implementations all currently target 4.1 Workflows. I've written test coverage for each world, and based the initial implementations for all of them based on world-postgres.

Is it possible for me to configure services in this manifest for other infra, such as mysql or infra emulation?

Summary

Registers seven community @fantasticfour/* world implementations in worlds-manifest.json so they're discoverable alongside the existing first-party and community worlds. Each entry includes its package name, repo/docs links, required env vars, and a credentials note when external infrastructure is needed.

Worlds added

ID Package Stack Notes
redis-simple @fantasticfour/world-redis Pure Redis (Lists-based queue) Self-hosted instance of Redis
redis-bullmq @fantasticfour/world-redis-bullmq Redis + BullMQ Production-ready via BullMQ
cloudflare @fantasticfour/world-cloudflare Cloudflare Durable Objects Edge runtime, requires deployment
mysql @fantasticfour/world-mysql Pure MySQL Works with PlanetScale, RDS, Aiven, etc.
azure @fantasticfour/world-azure Azure Cosmos DB + Service Bus Change Feed streaming
nats-jetstream @fantasticfour/world-nats-jetstream Self-hosted NATS JetStream Clustering supported
upstash @fantasticfour/world-upstash Upstash Redis + QStash Serverless / edge-ready

Other Worlds

I also have some other implementations for firestore Tasks, postgres + redis, mysql + redis, but they are more experimental and less practical.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented May 9, 2026

⚠️ No Changeset found

Latest commit: 4674ac4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 9, 2026

@vinnymac is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

Comment thread worlds-manifest.json Outdated
"credentialsNote": "Requires JAZZ_API_KEY, JAZZ_WORKER_ACCOUNT, and JAZZ_WORKER_SECRET from Jazz Cloud"
},
{
"id": "redis-simple",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we actually set this to fantasticfour-redis or similar? just realized we probably need to update the other community worlds too, to be less ambiguous. redis and redis-simple are confusing

Copy link
Copy Markdown
Contributor Author

@vinnymac vinnymac May 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with you, it's a bit confusing at the moment if this was to be merged as-is. I was wondering how we were going to handle this. Figured this was the perfect time to begin a discussion to address it.

I can make that change if you like, and update the others to include the published org or username?

Comment thread worlds-manifest.json Outdated
"setup": "pnpm exec fantasticfour-redis-setup"
},
{
"id": "redis-bullmq",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, let's update the id to fantasticfour-redis-bullmq?

Comment thread worlds-manifest.json
{
"id": "cloudflare",
"type": "community",
"package": "@fantasticfour/world-cloudflare",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fantasticfour-cloudflare

Comment thread worlds-manifest.json Outdated
"requiresDeployment": true
},
{
"id": "mysql",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same

Comment thread worlds-manifest.json Outdated
"setup": "pnpm exec world-mysql-setup"
},
{
"id": "azure",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same

Comment thread worlds-manifest.json Outdated
"credentialsNote": "Requires Azure Cosmos DB endpoint/key and Service Bus connection string"
},
{
"id": "nats-jetstream",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same

Comment thread worlds-manifest.json Outdated
"credentialsNote": "Requires NATS server with JetStream enabled (CI does not yet support nats service containers)"
},
{
"id": "upstash",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same

@pranaygp pranaygp requested a review from a team as a code owner May 12, 2026 18:50
@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented May 12, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
workflow-docs Ready Ready Preview, Comment, Open in v0 May 12, 2026 7:21pm

Register the Fantastic Four community world packages in the worlds manifest and show the Redis variants in the Embedded docs section.

Co-authored-by: Vincent Taverna <vinnymac@gmail.com>
Signed-off-by: Pranay Prakash <pranay.gp@gmail.com>
@pranaygp pranaygp merged commit e213447 into vercel:main May 14, 2026
4 of 20 checks passed
@github-actions
Copy link
Copy Markdown
Contributor

No backport to stable for e213447 (AI decision).

This commit modifies worlds-manifest.json and docs/components/worlds/WorldsFilteredGrid.tsx. The docs app file is outside docs/content/ and is not maintained on stable. The worlds manifest registers community worlds that target Workflow 4.1, which aligns with the main (beta) channel rather than the current stable GA series.

To override, re-run the Backport to stable workflow manually via workflow_dispatch with this commit SHA.

@pranaygp
Copy link
Copy Markdown
Contributor

merged! just fyi I had to squash the commit because of signed commit requirements on the repo

@pranaygp
Copy link
Copy Markdown
Contributor

Follow-up from trying to wire the Cloudflare community world into actual workbench e2e coverage: I think this is currently blocked by Workflow runtime itself, not by @fantasticfour/world-cloudflare's storage implementation.

@workflow/core still depends on Node's node:vm execution path (runInContext / VM contexts). In Cloudflare Workers, even with nodejs_compat, node:vm is exposed as a non-functional unenv stub. I verified a minimal Wrangler Worker importing node:vm and calling vm.runInContext() returns:

[unenv] vm.runInContext is not implemented yet!

So this world can still be useful as the Cloudflare-backed World adapter, but I don't think a workbench deployed directly to Workers can run the real Workflow e2e suite until Workflow has a Worker-compatible runtime path. I opened a central tracker here: #2028

The likely related unblocker is @TooTallNate's QuickJS snapshot runtime PR, which appears to remove the node:vm dependency as a side effect: #1300

I also opened the source-repo issue here: vinnymac/worlds#30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants