content: assess a maintained MDX rendering path

Aperta
  • Qualcosa non va?
#76 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown, next.js, react, typescript
Ambito
backend, content, security

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
8h 58m
PR unite (30g)
37

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di procoderji-com/procoderji

Tutte le issue di procoderji-com/procoderji

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.