content: assess a maintained MDX rendering path

Aberta
  • Algo errado?
#76 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
markdown, next.js, react, typescript
Domínio
backend, content, security

Direção de pesquisa

Start with src/components/note-body.tsx, SAFE_MDX_OPTIONS, and the current next-mdx-remote dependency; compare maintained alternatives with a narrowly scoped maintenance strategy. Review the compatibility, licensing, runtime and bundle effects, maintenance cost, and issues #38 and #73 before documenting a choice. Done means the comparison supports the approach, safety and compatibility requirements are preserved, and the specified production-build and browser tests pass.

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

Descrição

dependencies enhancement help wanted

Maintenance finding

The upstream hashicorp/next-mdx-remote repository is archived as of this review (2026-11-10). This project currently pins version 6.0.0 and uses next-mdx-remote/rsc in src/components/note-body.tsx.

Sources: upstream repository and license. The current dependency audit reported no known production vulnerability; archival is a maintenance concern, not evidence of an active exploit.

Scope

  • Compare a maintained rendering approach with a narrowly scoped maintenance strategy for the current renderer. Record compatibility, licensing, bundle/runtime effects and maintenance cost before adding a replacement dependency.
  • Preserve SAFE_MDX_OPTIONS: reject raw HTML, JSX and expressions instead of evaluating or silently dropping them.
  • Preserve link/image sanitization, same-site image policy and filesystem/path isolation.
  • Keep the reviewed Markdown/MDX content contract, metadata, static generation and active dashboard/guide readers compatible.
  • Coordinate with #38 (Markdown tables) and #73 (legacy reader cleanup), so those tasks do not create a second rendering pipeline.
  • Document the selected approach and any migration steps; keep this separate from executing arbitrary student-supplied MDX.

Done when

A recorded comparison supports the chosen implementation, any new dependency is reviewed, and existing content safety, rendering, production-build and browser tests pass. Malicious HTML/JSX/expression and invalid-link fixtures remain rejected. Original learning content and its public URLs keep working.

Linguagem predominante
TypeScript
Estrelas
1
Forks
1
Merge médio
8h 58min
PRs com merge (30d)
37

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 procoderji-com/procoderji

Todas as issues de procoderji-com/procoderji

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.