content: assess a maintained MDX rendering path

Abierto
  • ¿Algo no está bien?
#76 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown, next.js, react, typescript
Área
backend, content, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
8 h 58 min
PR fusionados (30 d)
37

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de procoderji-com/procoderji

Todos los issues de procoderji-com/procoderji

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.