What breaks when you ship Next.js on Cloudflare Workers

May 16, 2026 · 7:20 PM UTC ·4 min read · 0 reactions · 0 comments · 28 views

TL;DR · WeSearch summary

The article discusses the challenges of deploying Next.js applications on Cloudflare Workers. It highlights the need to replace certain Node.js dependencies with compatible alternatives for the Workers environment. Additionally, it outlines specific implementation details and workarounds encountered during the development process.

Key facts

▪Cloudflare Workers do not support Node.js, requiring developers to find compatible packages.
▪The author replaced bcrypt with Argon2id for password hashing due to compatibility issues.
▪The article details the process of handling Yahoo Finance's crumb token for API requests.

How this story was covered

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.

Centre · 1

▪ What breaks when you ship Next.js on Cloudflare Workers — Finterm

About this source

DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.

All DEV.to (Top) coverage →

Original article

DEV.to (Top)

Read full at DEV.to (Top) →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

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	DEV.to (Top)
Canonical URL	https://dev.to/m0dus/what-breaks-when-you-ship-nextjs-on-cloudflare-workers-k73
Publication time	Sat, 16 May 2026 19:20:09 +0000
Retrieval time	2026-05-16T19:40:19.037Z
Last seen	2026-05-16T19:40:19.037Z
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)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

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.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3882394) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } William March Posted on May 16 • Originally published at finterm.xyz What breaks when you ship Next.js on Cloudflare Workers #webdev #nextjs #javascript #cloudflare 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 DEV.to (Top).

Anonymous · no account needed

Discussion

0 comments