Add ElastiCache (Valkey) message queue template#1309
Add ElastiCache (Valkey) message queue template#1309vasigorc wants to merge 12 commits intovercel:mainfrom
Conversation
|
@vasigorc is attempting to deploy a commit to the Vercel Labs Team on Vercel. A member of the Team first needs to authorize it. |
acarbonetto
left a comment
There was a problem hiding this comment.
Interesting idea, to you message processing instead of a basic API.
| return { | ||
| valid: true, | ||
| data: { | ||
| name: data.name.trim(), |
There was a problem hiding this comment.
Here, like on two lines below, the intent is to trim trailing white spaces/tabs.
There was a problem hiding this comment.
Right. But maybe the extra whitespace is desired.
And if not, garbage in, garbage out.
| // Clear form | ||
| setName('') | ||
| setEmail('') | ||
| setMessage('') |
There was a problem hiding this comment.
nit: I'd suggest not clearing the form? But I dont have strong feelings.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
c2490d7 to
b6c014a
Compare
Demonstrates Streams with consumer groups for message queue functionality in Vercel Functions. Includes: - Contact form message producer (POST /api/messages) - Consumer group message processor with XREADGROUP and XAUTOCLAIM (GET /api/messages) - Message acknowledgement endpoint (DELETE /api/messages) - UI components for form submission and message processing - valkey-glide client integration with proper error handling
Co-authored-by: Andrew Carbonetto <andrew.carbonetto@improving.com>
`serverComponentsExternalPackages` moved out of `experimental` in Next.js 15+
getMetadata is not compatible with client components
b6c014a to
9e0410f
Compare
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Deployment failed with the following error: Learn More: https://vercel.com/docs/concepts/projects/project-configuration |
There was a problem hiding this comment.
Could you please add a packageManager and engines field, with Node version of at least 24 and a pnpm version of at least 10?
packageManager is required for turborepo compatibility.
For example:
"packageManager": "pnpm@10.29.2",
"engines": {
"node": "24.x",
"pnpm": "10.29.2"
},
| @@ -0,0 +1,30 @@ | |||
| { | |||
| "name": "message-queue-elasticache", | |||
There was a problem hiding this comment.
Given that we have other examples in this directory that start with aws- could we rename this (and its parent directory) to something like aws-message-queue-elaticache?
There was a problem hiding this comment.
Could you use export default and postcss.config.mjs?
There was a problem hiding this comment.
Please remove this and use Tailwind v4 (which does not use a tailwind.config file)
| @@ -0,0 +1,31 @@ | |||
| { | |||
| "compilerOptions": { | |||
| "target": "es5", | |||
There was a problem hiding this comment.
this looks like a typo.
I would recommend deleting your tsconfig.json and then running pnpm dev — Next.js will automatically generate the correct tsconfig.json file. If you need different options for build or testing, create separate tsconfig files.
There was a problem hiding this comment.
please install @vercel/config and use vercel.ts
More info here:
| { | ||
| "$schema": "https://turborepo.com/schema.json", | ||
| "pipeline": { | ||
| "build": { |
| "eslint-config-next": "^13.4.10", | ||
| "postcss": "^8.4.26", | ||
| "tailwindcss": "^3.3.3", | ||
| "turbo": "^1.10.8", |
There was a problem hiding this comment.
Update turbo, the latest version is 2.9.9
Description
Adds a template demonstrating AWS ElastiCache integration for message queue functionality using Redis Streams.
What this template shows
Type of Change
Simple demo flow looks like this:
Screen.Recording.2025-11-25.at.4.13.35.PM.mov
New Example Checklist
npm run new-examplewas used to create the example