Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Run the docs site's chat endpoint on the Cloudflare adapter

Geschlossen
  • Stimmt etwas nicht?
#202 5 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@Pratham2511 arbeitet bereits daran.

Seit 21.10.2026.

  • #297 von @Pratham2511 — gemerged

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
72/100
Issue-Typ
Refactoring
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
api, backend

Rechercherichtung

Read website/src/pages/api/chat.ts and the chatcopsCloudflareHandler adapter from @chatcops/server/cloudflare, then check how locals.runtime.ctx is provided by @astrojs/cloudflare. Replace the endpoint's custom stream handling with the adapter while preserving rate limiting and cf-connecting-ip handling, and configure the site's origin for CORS. Done when OPTIONS and POST return the same origin header and the website build and local chat work as described in the issue.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

hacktoberfest help wanted website

The docs site's chat endpoint (website/src/pages/api/chat.ts) builds its own SSE response around handleChat (the POST handler from line 79) instead of using chatcopsCloudflareHandler from @chatcops/server/cloudflare. The site runs on Cloudflare Workers, so it should run the same adapter users do: that way the site tests it, and fixes like #195 (stop the provider when the visitor leaves) don't have to be copied by hand. The OPTIONS handler (line 133) also answers Access-Control-Allow-Origin: * while POST sends no CORS header at all.

What to do

  • Build the adapter once per isolate, the same lazy way the file builds the handler today (the API key only exists inside a request through getSecret), and call it from POST and OPTIONS.
  • Pass the Workers context so waitUntil works. With @astrojs/cloudflare 14 it's locals.cfContext (locals.runtime.ctx was removed and throws). ogcops does the same in src/pages/api/og.ts.
  • Set cors to the site's own origin (https://chat.codercops.com) instead of *.
  • Keep the rate limiting and the cf-connecting-ip handling the file has now.

Acceptance criteria

  • website/src/pages/api/chat.ts no longer has its own stream loop
  • The chat on the site still works locally with pnpm --filter @chatcops/website dev (say how you tested it)
  • OPTIONS and POST send the same Access-Control-Allow-Origin
  • pnpm --filter @chatcops/website build succeeds
  • No changeset needed (website only)

Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off dev, and open your PR against dev with Closes #<this issue number>. Setup notes (pnpm, build before test) are in CONTRIBUTING.md.

Vorherrschende Sprache
TypeScript
Sterne
13
Forks
7
Ø Merge
3 Std. 33 Min.
Gemergte PRs (30 T.)
176

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus codercops/chatcops

Alle Issues in codercops/chatcops

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.