opennextjs/opennextjs-netlify

Open Next.js adapter for Netlify

View on GitHub ↗Jump to charts ↓

opennextjs/opennextjs-netlify has 850+ stars and 100+ forks on GitHub, is written in TypeScript, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on June 19th, 2025
Created on October 26th, 2020
Open Issues & Pull Requests: 109 (+0)
GitHub issues: Enabled
Number of forks: 116
Total Stargazers: 854 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 186.9 days
Mean response time: 254.6 days
90th percentile: 705.1 days
Tracked items: 107

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

76% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 51
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 384 days
Stale 30+ days: 48
Stale 90+ days: 42

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type: bug (177)
  • v4 (57)
  • priority: medium (36)
  • priority: low (32)
  • priority: high (30)
  • Next.js e2e test failure (29)
  • type: feature (23)
  • status: awaiting user response (22)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

The opennextjs-netlify repository is a TypeScript-based adapter that enables Next.js applications to run natively on Netlify's platform. It handles the complete build process and runtime environment configuration for Next.js sites deployed to Netlify, functioning as an automatic plugin that integrates seamlessly into Netlify's deployment pipeline. The package is published as @netlify/plugin-nextjs on npm and operates under an MIT License.

The primary purpose of this repository is to bridge Next.js and Netlify's infrastructure, allowing developers to deploy modern React-based applications without requiring manual configuration in most cases. Next.js support is native to Netlify, meaning the runtime installs and operates automatically during builds for Next.js projects. The adapter supports Next.js 13.5 or later with Node.js 18 or later, establishing clear version requirements for compatibility. Users can deploy directly through Netlify's build system with zero additional setup, or they can manually install the runtime through Netlify's UI or via npm with explicit version pinning through netlify.toml configuration.

The repository maintains two major version lines. Version 5 represents the current standard for modern Next.js deployments, while version 4 continues to support legacy environments running Next.js 10-13.4 or Node.js versions below 18. The v4 branch receives only security and critical bug fixes, with separate documentation maintained for users still operating on that version. This dual-version approach ensures backward compatibility while allowing the main codebase to advance with current platform standards.

The repository's classification spans frontend development, serverless functions, React frameworks, and JAMstack architecture, reflecting its role in the modern web development ecosystem. It bridges static site generation, server-side rendering, and API routes within the Next.js framework while leveraging Netlify's deployment and continuous integration capabilities.

Users encountering issues are directed to the GitHub issue tracker, while feature requests and general feedback flow through the discussion board. The documentation emphasizes that most Next.js developers will never need to manually interact with this package, as Netlify handles installation and updates automatically, though advanced users can pin specific versions for production stability. The project represents a critical infrastructure component for the Next.js-on-Netlify deployment experience, abstracting away platform-specific complexity while maintaining compatibility across multiple Next.js and Node.js versions.