content: assess a maintained MDX rendering path
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- TypeScript
- 星标
- 1
- 派生
- 1
- 平均合并
- 8 小时 58 分钟
- 30 天内合并 PR
- 37
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
procoderji-com/procoderji 的其他 Issue
-
area:frontend bug
难度 2/5 1-3 小时 新手友好度 62/100
procoderji-com/procoderji#104 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 88/100
procoderji-com/procoderji#36 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 85/100
procoderji-com/procoderji#35 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 79/100
procoderji-com/procoderji#34 ·
维护者通常 1 天内回复
-
enhancement good first issue
难度 1/5 1-3 小时 新手友好度 90/100
procoderji-com/procoderji#33 ·
维护者通常 1 天内回复
查看 procoderji-com/procoderji 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug platform-android
难度 2/5 1-3 小时 新手友好度 68/100
Termix-SSH/Mobile#146 · 1 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
devswha/herdr-web-ui#3875 ·
-
难度 1/5 1 小时以内 新手友好度 88/100
-
area: runtime chore cli consistency dependencies developer-experience difficulty: easy discovery documentation enhancement good first issue help wanted hygiene json-output packaging priority: P3 tests version
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复