What breaks when you ship Next.js on Cloudflare Workers
The article discusses the challenges of deploying Next.js applications on Cloudflare Workers. It highlights specific npm packages that are incompatible with the Workers runtime and suggests alternatives. The author shares insights on handling session cookies and optimizing caching patterns for better performance.
- ▪Common npm packages like bcrypt and cheerio do not work in the Cloudflare Workers runtime.
- ▪The author replaced bcrypt with Argon2id and cheerio with htmlparser2 for better compatibility.
- ▪Session management with Yahoo Finance requires a specific handshake process to obtain necessary cookies and tokens.
2 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ What breaks when you ship Next.js on Cloudflare Workers — DEV.to (Top)
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Finterm |
| Canonical URL | https://finterm.xyz/blog/nextjs-on-cloudflare-workers |
| Publication time | Sat, 16 May 2026 20:10:40 +0000 |
| Retrieval time | 2026-05-16T20:40:19.047Z |
| Last seen | 2026-05-16T20:40:19.047Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | LIelk7U56J8l · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
← Back to blogMay 16, 2026· cloudflare · nextjs · javascriptWhat breaks when you ship Next.js on Cloudflare WorkersA log of which npm packages don't survive the Workers runtime, what to swap them with, and the patterns that ended up mattering.I've been building Finterm, a financial terminal that runs entirely in a browser tab, on Cloudflare Workers via @opennextjs/cloudflare. The promise is the obvious one — global edge runtime, near-zero cold starts, pay-per-request pricing. The catch is that Workers don't run Node.js.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Finterm.
Discussion
0 commentsMore from Finterm
