You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] README's Node.js prerequisite is now wrong — needs 20.9+, not 18+ #1776
Bug description
README.md's Prerequisites section (line 108) says "Node.js 18+". Since the Next.js 15→16 upgrade (merged in #1766), Next.js itself requires Node.js 20.9.0 or later — Node 18 is no longer supported by the framework. A new contributor following the README's own instructions on Node 18 would hit a confusing failure.
Steps to reproduce
Compare README.md:108 against Next.js 16's actual Node requirement (documented in Next's own release notes / next --version compatibility check).
Expected behavior
"Node.js 20.9+".
Actual behavior
Stale prerequisite from before the framework upgrade.
Activity
github-actions commentedon Sep 15, 2026
👋 Thanks for opening an issue, @magic-peach!
Our maintainers will review this shortly 🚀
Before you start working
For GSSoC'26 contributors
If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:
Architecture notes
Reframe is a static Next.js app with
output: "export". Key points:headers()innext.config.tswon't work — usevercel.jsoninsteadnot-found.tsxrequirespublic/404.html+vercel.jsonroutes configHappy contributing! ⭐ Star the repo if you find it useful!
github-actions commentedon Sep 15, 2026
Claude encountered an error —— View job
I'll analyze this and get back to you.
Mohamedajab commentedon Oct 8, 2026
/assign
github-actions commentedon Oct 8, 2026
Hey @Mohamedajab, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.
github-actions commentedon Oct 10, 2026
Hey @Mohamedajab, just a friendly reminder that this issue has had no activity for 2 days. Please leave an update or let us know if you need help! ⏰
github-actions commentedon Oct 14, 2026
Hey @Mohamedajab, final warning!⚠️ This issue has had no activity for 4 days and will be automatically unassigned in 24 hours if there is no update.
github-actions commentedon Oct 19, 2026
This issue has been unassigned from @Mohamedajab due to 5 days of inactivity and is open for anyone to pick up — comment
/assignto claim it!