Skip to content

[BUG] README's Node.js prerequisite is now wrong — needs 20.9+, not 18+ #1776

Open

Description

@magic-peach

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

  1. github-actions commented on Sep 15, 2026

    @github-actions
    Contributor

    👋 Thanks for opening an issue, @magic-peach!

    Our maintainers will review this shortly 🚀

    Before you start working

    • 📖 Read the CONTRIBUTING.md guide
    • 💬 Wait for a maintainer to assign you the issue before starting work
    • 🔍 Search for existing issues to avoid duplicates

    For GSSoC'26 contributors

    If you're contributing under GirlScript Summer of Code 2026, please mention it in your comment when requesting assignment:

    "I'd like to work on this — contributing under GSSoC'26"

    Architecture notes

    Reframe is a static Next.js app with output: "export". Key points:

    • All video processing uses FFmpeg.wasm (client-side, no server)
    • headers() in next.config.ts won't work — use vercel.json instead
    • not-found.tsx requires public/404.html + vercel.json routes config

    Happy contributing! ⭐ Star the repo if you find it useful!

  2. github-actions commented on Sep 15, 2026

    @github-actions
    Contributor

    Claude encountered an error —— View job


    I'll analyze this and get back to you.

  3. Mohamedajab commented on Oct 8, 2026

    @Mohamedajab

    /assign

  4. github-actions commented on Oct 8, 2026

    @github-actions
    Contributor

    Hey @Mohamedajab, this issue has been assigned to you! 🎉 Please make progress within 5 days or it will be automatically unassigned due to inactivity.

  5. github-actions commented on Oct 10, 2026

    @github-actions
    Contributor

    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! ⏰

  6. github-actions commented on Oct 14, 2026

    @github-actions
    Contributor

    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.

  7. github-actions commented on Oct 19, 2026

    @github-actions
    Contributor

    This issue has been unassigned from @Mohamedajab due to 5 days of inactivity and is open for anyone to pick up — comment /assign to claim it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working correctlydocumentationDocumentation improvementgssoc'26GirlScript Summer of Code 2026level:beginnerBeginner level - 20 ptspriority: mediumMedium prioritytype:bugBug fixtype:docsDocumentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions