Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

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

Fechada
  • Algo errado?
#202 5 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 1 dia

@Pratham2511 já está trabalhando nisso.

Desde 21/10/2026.

  • #297 de @Pratham2511 — integrado

Avaliação

Dificuldade
3/5
Tempo estimado
1-2 dias
Facilidade para iniciantes
72/100
Tipo de issue
Refatoração
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
typescript
Domínio
api, backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
13
Forks
7
Merge médio
3h 33min
PRs com merge (30d)
176

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de codercops/chatcops

Todas as issues de codercops/chatcops

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.