Skip to content

fix: align supported Cloudflare runtime dependencies - #11

Draft
ofershap wants to merge 1 commit into
mainfrom
fix/cloudflare-runtime-compatibility
Draft

ofershap wants to merge 1 commit into
mainfrom
fix/cloudflare-runtime-compatibility

Conversation

@ofershap

Copy link
Copy Markdown
Owner

Pin a supported dependency set: Next and eslint-config-next 16.4.6, OpenNext Cloudflare 1.20.17, Wrangler 4.162.0. Keep runtime config, middleware and billing unchanged.

The old local workerd fixture failed before rendering with an unsupported dynamic middleware-manifest require. The supported stack builds and renders the same public-data profile locally and on isolated provider Workers. This is compatibility evidence, not proof that production resource-limit errors have the same cause or that cold rendering fits the free CPU budget.

Also excludes generated OpenNext/Wrangler output from lint and adds three regression tests for the existing Cache API adapter: read/write/type isolation, read-only KV fallback and deletion. Five tests and full source lint pass (0 errors, 9 warnings). Next/OpenNext builds pass. Local native profile/search desktop and mobile views render without JS errors.

Remaining release checks: real API and ISR/queue behavior need broader local regression coverage. The combined unknown-script provider metrics cannot qualify cold CPU. The public-data fixtures had no runtime secrets or production storage bindings and have been deleted.

The lockfile advisory report falls from 26 package findings (2 critical) to 10 (no critical). This is not an exploitation claim. Critical Next advisories have Windows/image-optimization/use-cache prerequisites not established in this Cloudflare app; proxy-addr enters via adapter build tooling. No audit-force or security bypass used.

Keep draft. Independent of payload projection and cache PR #8; no production promotion from fixture HTTP 200 alone.

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.

1 participant