Next.js 15 is officially stable and ready for production. This release builds on the updates from bothRC1 andRC2. We've focused heavily on stability while adding some exciting updates we think you'll love. Try Next.js 15 today:

# Use the new automated upgrade CLInpx@next/codemod@canaryupgradelatest# ...or upgrade manuallynpminstallnext@latestreact@rcreact-dom@rc

We're also excited to share more about what's coming next atNext.js Conf this Thursday, October 24th.

Here's what is new in Next.js 15:

• @next/codemod CLI: Easily upgrade to the latest Next.js and React versions.
• Async Request APIs (Breaking): Incremental step towards a simplified rendering and caching model.
• Caching Semantics (Breaking):fetch requests,GET Route Handlers, and client navigations are no longer cached by default.
• React 19 Support: Support for React 19, React Compiler (Experimental), and hydration error improvements.
• Turbopack Dev (Stable): Performance and stability improvements.
• Static Indicator: New visual indicator shows static routes during development.
• unstable_after API (Experimental): Execute code after a response finishes streaming.
• instrumentation.js API (Stable): New API for server lifecycle observability.
• Enhanced Forms (next/form): Enhance HTML forms with client-side navigation.
• next.config: TypeScript support fornext.config.ts.
• Self-hosting Improvements: More control overCache-Control headers.
• Server Actions Security: Unguessable endpoints and removal of unused actions.
• Bundling External Packages (Stable): New config options for App and Pages Router.
• ESLint 9 Support: Added support for ESLint 9.
• Development and Build Performance: Improved build times and Faster Fast Refresh.

Smooth upgrades with@next/codemod CLI

We include codemods (automated code transformations) with every major Next.js release to help automate upgrading breaking changes.

To make upgrades even smoother, we've released an enhanced codemod CLI:

npx@next/codemod@canaryupgradelatest

This tool helps you upgrade your codebase to the latest stable or prerelease versions. The CLI will update your dependencies, show available codemods, and guide you through applying them.

Thecanary tag uses the latest version of the codemod while the latest specifies the Next.js version. We recommend using the canary version of the codemod even if you are upgrading to the latest Next.js version, as we plan to continue adding improvements to the tool based on your feedback.

Learn more aboutNext.js codemod CLI.

Async Request APIs (Breaking Change)

In traditional Server-Side Rendering, the server waits for a request before rendering any content. However, not all components depend on request-specific data, so it's unnecessary to wait for the request to render them. Ideally, the server would prepare as much as possible before a request arrives. To enable this, and set the stage for future optimizations, we need to know when to wait for the request.

Therefore, we are transitioning APIs that rely on request-specific data—such asheaders,cookies,params, andsearchParams—to beasynchronous.

import { cookies }from'next/headers';exportasyncfunctionAdminPanel() {constcookieStore=awaitcookies();consttoken=cookieStore.get('token');// ...}

This is abreaking change and affects the following APIs:

• cookies
• headers
• draftMode
• params inlayout.js,page.js,route.js,default.js,generateMetadata, andgenerateViewport
• searchParams inpage.js

For an easier migration, these APIs can temporarily be accessed synchronously, but will show warnings in development and production until the next major version. Acodemod is available to automate the migration:

npx@next/codemod@canarynext-async-request-api.

For cases where the codemod can't fully migrate your code, please read theupgrade guide. We have also provided anexample of how to migrate a Next.js application to the new APIs.

Caching Semantics

Next.js App Router launched with opinionated caching defaults. These were designed to provide the most performant option by default with the ability to opt out when required.

Based on your feedback, we re-evaluated ourcaching heuristics and how they would interact with projects like Partial Prerendering (PPR) and with third party libraries usingfetch.

With Next.js 15, we're changing the caching default forGET Route Handlers and the Client Router Cache from cached by default to uncached by default. If you want to retain the previous behavior, you can continue to opt-into caching.

We're continuing to improve caching in Next.js in the coming months and we'll share more details soon.

GET Route Handlers are no longer cached by default

In Next 14, Route Handlers that used theGET HTTP method were cached by default unless they used a dynamic function or dynamic config option. In Next.js 15,GET functions arenot cached by default.

You can still opt into caching using a static route config option such asexport dynamic = 'force-static'.

Special Route Handlers likesitemap.ts,opengraph-image.tsx, andicon.tsx, and othermetadata files remain static by default unless they use dynamic functions or dynamic config options.

Client Router Cache no longer caches Page components by default

In Next.js 14.2.0, we introduced an experimentalstaleTimes flag to allow custom configuration of theRouter Cache.

In Next.js 15, this flag still remains accessible, but we are changing the default behavior to have astaleTime of0 for Page segments. This means that as you navigate around your app, the client will always reflect the latest data from the Page component(s) that become active as part of the navigation. However, there are still important behaviors that remain unchanged:

• Shared layout data won't be refetched from the server to continue to supportpartial rendering.
• Back/forward navigation will still restore from cache to ensure the browser can restore scroll position.
• loading.js will remain cached for 5 minutes (or the value of thestaleTimes.static configuration).

You can opt into the previous Client Router Cache behavior by setting the following configuration:

constnextConfig= {  experimental: {    staleTimes: {      dynamic:30,    },  },};exportdefault nextConfig;

React 19

As part of the Next.js 15 release, we've made the decision to align with the upcoming release of React 19.

In version 15, the App Router uses React 19 RC, and we've also introduced backwards compatibility for React 18 with the Pages Router based on community feedback. If you're using the Pages Router, this allows you to upgrade to React 19 when ready.

Although React 19 is still in the RC phase, our extensive testing across real-world applications and our close work with the React team have given us confidence in its stability. The core breaking changes have been well-tested and won't affect existing App Router users. Therefore, we've decided to release Next.js 15 as stable now, so your projects are fully prepared for React 19 GA.

To ensure the transition is as smooth as possible, we've providedcodemods and automated tools to help ease the migration process.

Read theNext.js 15 upgrade guide, theReact 19 upgrade guide, and watch theReact Conf Keynote to learn more.

Pages Router on React 18

Next.js 15 maintains backward compatibility for the Pages Router with React 18, allowing users to continue using React 18 while benefiting from improvements in Next.js 15.

Since the first Release Candidate (RC1), we've shifted our focus to include support for React 18 based on community feedback. This flexibility enables you to adopt Next.js 15 while using the Pages Router with React 18, giving you greater control over your upgrade path.

Note: While it is possible to run the Pages Router on React 18 and the App Router on React 19 in the same application, we don't recommend this setup. Doing so could result in unpredictable behavior and typings inconsistencies, as the underlying APIs and rendering logic between the two versions may not fully align.

React Compiler (Experimental)

TheReact Compiler is a new experimental compiler created by the React team at Meta. The compiler understands your code at a deep level through its understanding of plain JavaScript semantics and theRules of React, which allows it to add automatic optimizations to your code. The compiler reduces the amount of manual memoization developers have to do through APIs such asuseMemo anduseCallback - making code simpler, easier to maintain, and less error prone.

With Next.js 15, we've added support for theReact Compiler. Learn more about the React Compiler, and theavailable Next.js config options.

Note: The React Compiler is currently only available as a Babel plugin, which will result in slower development and build times.

Hydration error improvements

Next.js 14.1made improvements to error messages and hydration errors. Next.js 15 continues to build on those by adding an improved hydration error view. Hydration errors now display the source code of the error with suggestions on how to address the issue.

For example, this was a previous hydration error message in Next.js 14.1:

Next.js 15 has improved this to:

Turbopack Dev

We are happy to announce thatnext dev --turbo is nowstable and ready to speed up your development experience. We've been using it to iterate onvercel.com,nextjs.org,v0, and all of our other applications with great results.

For example, withvercel.com, a large Next.js app, we've seen:

• Up to76.7% faster local server startup.
• Up to96.3% faster code updates with Fast Refresh.
• Up to45.8% faster initial route compile without caching (Turbopack does not have disk caching yet).

You can learn more about Turbopack Dev in our newblog post.

Static Route Indicator

Next.js now displays a Static Route Indicator during development to help you identify which routes are static or dynamic. This visual cue makes it easier to optimize performance by understanding how your pages are rendered.

You can also use thenext build output to view the rendering strategy for all routes.

This update is part of our ongoing efforts to enhance observability in Next.js, making it easier for developers to monitor, debug, and optimize their applications. We're also working on dedicated developer tools, with more details to come soon.

Learn more about theStatic Route Indicator, which can be disabled.

Executing code after a response withunstable_after (Experimental)

When processing a user request, the server typically performs tasks directly related to computing the response. However, you may need to perform tasks such as logging, analytics, and other external system synchronization.

Since these tasks are not directly related to the response, the user should not have to wait for them to complete. Deferring the work after responding to the user poses a challenge because serverless functions stop computation immediately after the response is closed.

after() is a new experimental API that solves this problem by allowing you to schedule work to be processed after the response has finished streaming, enabling secondary tasks to run without blocking the primary response.

To use it, addexperimental.after tonext.config.js:

constnextConfig= {  experimental: {    after:true,  },};exportdefault nextConfig;

Then, import the function in Server Components, Server Actions, Route Handlers, or Middleware.

import { unstable_afteras after }from'next/server';import { log }from'@/app/utils';exportdefaultfunctionLayout({ children }) {// Secondary taskafter(()=> {log();  });// Primary taskreturn <>{children}</>;}

Learn more aboutunstable_after.

instrumentation.js (Stable)

Theinstrumentation file, with theregister() API, allows users to tap into the Next.js server lifecycle to monitor performance, track the source of errors, and deeply integrate with observability libraries likeOpenTelemetry.

This feature is nowstable and theexperimental.instrumentationHook config option can be removed.

In addition, we've collaborated withSentry on designing a newonRequestError hook that can be used to:

• Capture important context about all errors thrown on the server, including:
  • Router: Pages Router or App Router
  • Server context: Server Component, Server Action, Route Handler, or Middleware
• Report the errors to your favorite observability provider.

exportasyncfunctiononRequestError(err, request, context) {awaitfetch('https://...', {    method:'POST',    body:JSON.stringify({ message:err.message, request, context }),    headers: {'Content-Type':'application/json' },  });}exportasyncfunctionregister() {// init your favorite observability provider SDK}

Learn more about theonRequestErrorfunction.

<Form> Component

The new<Form> component extends the HTML<form> element withprefetching,client-side navigation, and progressive enhancement.

It is useful for forms that navigate to a new page, such as a search form that leads to a results page.

import Formfrom'next/form';exportdefaultfunctionPage() {return (    <Formaction="/search">      <inputname="query" />      <buttontype="submit">Submit</button>    </Form>  );}

The<Form> component comes with:

• Prefetching: When the form is in view, thelayout andloading UI are prefetched, making navigation fast.
• Client-side Navigation: On submission, shared layouts and client-side state are preserved.
• Progressive Enhancement: If JavaScript hasn't loaded yet, the form still works via full-page navigation.

Previously, achieving these features required a lot of manual boilerplate. For example:

// Note: This is abbreviated for demonstration purposes.// Not recommended for use in production code.'use client'import { useEffect }from'react'import { useRouter }from'next/navigation'exportdefaultfunctionForm(props) {constaction=props.actionconstrouter=useRouter()useEffect(()=> {// if form target is a URL, prefetch itif (typeof action==='string') {router.prefetch(action)    }  }, [action, router])functiononSubmit(event) {event.preventDefault()// grab all of the form fields and trigger a `router.push` with the data URL encodedconstformData=newFormData(event.currentTarget)constdata=newURLSearchParams()for (const [name,value]of formData) {data.append(name, valueasstring)    }router.push(`${action}?${data.toString()}`)  }if (typeof action==='string') {return <formonSubmit={onSubmit} {...props} />  }return <form {...props} />}

Learn more about the<Form> Component.

Support fornext.config.ts

Next.js now supports the TypeScriptnext.config.ts file type and provides aNextConfig type for autocomplete and type-safe options:

importtype { NextConfig }from'next';constnextConfig:NextConfig= {/* config options here */};exportdefault nextConfig;

Learn more aboutTypeScript support in Next.js.

Improvements for self-hosting

When self-hosting applications, you may need more control overCache-Control directives.

One common case is controlling thestale-while-revalidate period sent for ISR pages. We've implemented two improvements:

1. You can now configure theexpireTime value innext.config. This was previously theexperimental.swrDelta option.
2. Updated the default value to one year, ensuring most CDNs can fully apply thestale-while-revalidate semantics as intended.

We also no longer override customCache-Control values with our default values, allowing full control and ensuring compatibility with any CDN setup.

Finally, we've improved image optimization when self-hosting. Previously, we recommended you installsharp for optimizing images on your Next.js server. This recommendation was sometimes missed. With Next.js 15, you no longer need to manually installsharp — Next.js will usesharp automatically when usingnext start or running withstandalone output mode.

To learn more, see our newdemo and tutorial video on self-hosting Next.js.

Enhanced Security for Server Actions

Server Actions are server-side functions that can be called from the client. They are defined by adding the'use server' directive at the top of a file and exporting an async function.

Even if a Server Action or utility function is not imported elsewhere in your code, it's still a publicly accessible HTTP endpoint. While this behavior is technically correct, it can lead to unintentional exposure of such functions.

To improve security, we've introduced the following enhancements:

• Dead code elimination: Unused Server Actions won't have their IDs exposed to the client-side JavaScript bundle, reducing bundle size and improving performance.
• Secure action IDs: Next.js now creates unguessable, non-deterministic IDs to allow the client to reference and call the Server Action. These IDs are periodically recalculated between builds for enhanced security.

// app/actions.js'use server';// This action **is** used in our application, so Next.js// will create a secure ID to allow the client to reference// and call the Server Action.exportasyncfunctionupdateUserAction(formData) {}// This action **is not** used in our application, so Next.js// will automatically remove this code during `next build`// and will not create a public endpoint.exportasyncfunctiondeleteUserAction(formData) {}

You should still treat Server Actions as public HTTP endpoints. Learn more aboutsecuring Server Actions.

Optimizing bundling of external packages (Stable)

Bundling external packages can improve the cold start performance of your application. In theApp Router, external packages are bundled by default, and you can opt-out specific packages using the newserverExternalPackages config option.

In thePages Router, external packages are not bundled by default, but you can provide a list of packages to bundle using the existingtranspilePackages option. With this configuration option, you need to specify each package.

To unify configuration between App and Pages Router, we're introducing a new option,bundlePagesRouterDependencies to match the default automatic bundling of the App Router. You can then useserverExternalPackages to opt-out specific packages, if needed.

constnextConfig= {// Automatically bundle external packages in the Pages Router:  bundlePagesRouterDependencies:true,// Opt specific packages out of bundling for both App and Pages Router:  serverExternalPackages: ['package-name'],};exportdefault nextConfig;

Learn more aboutoptimizing external packages.

ESLint 9 Support

Next.js 15 also introduces support forESLint 9, following the end-of-life for ESLint 8 on October 5, 2024.

To ensure a smooth transition, Next.js remain backwards compatible, meaning you can continue using either ESLint 8 or 9.

If you upgrade to ESLint 9, and we detect that you haven't yet adoptedthe new config format, Next.js will automatically apply theESLINT_USE_FLAT_CONFIG=false escape hatch to ease migration.

Additionally, deprecated options like—ext and—ignore-path will be removed when runningnext lint. Please note that ESLint will eventually disallow these older configurations in ESLint 10, so we recommend starting your migration soon.

For more details on these changes, check out themigration guide.

As part of this update, we've also upgradedeslint-plugin-react-hooks tov5.0.0, which introduces new rules for React Hooks usage. You can review all changes in thechangelog for eslint-plugin-react-hooks@5.0.0.

Development and Build Improvements

Server Components HMR

During development, Server components are re-executed when saved. This means, anyfetch requests to your API endpoints or third-party services are also called.

To improve local development performance and reduce potential costs for billed API calls, we now ensure Hot Module Replacement (HMR) can re-usefetch responses from previous renders.

Learn more about theServer Components HMR Cache.

Faster Static Generation for the App Router

We've optimized static generation to improve build times, especially for pages with slow network requests.

Previously, our static optimization process rendered pages twice—once to generate data for client-side navigation and a second time to render the HTML for the initial page visit. Now, we reuse the first render, cutting out the second pass, reducing workload and build times.

Additionally, static generation workers now share thefetch cache across pages. If afetch call doesn't opt out of caching, its results are reused by other pages handled by the same worker. This reduces the number of requests for the same data.

Advanced Static Generation Control (Experimental)

We've added experimental support for more control over the static generation process for advanced use cases that would benefit from greater control.

We recommend sticking to the current defaults unless you have specific requirements as these options can lead to increased resource usage and potential out-of-memory errors due to increased concurrency.

constnextConfig= {  experimental: {// how many times Next.js will retry failed page generation attempts// before failing the build    staticGenerationRetryCount:1// how many pages will be processed per worker    staticGenerationMaxConcurrency:8// the minimum number of pages before spinning up a new export worker    staticGenerationMinPagesPerWorker:25  },}exportdefault nextConfig;

Learn more about theStatic Generation options.

Other Changes

• [Breaking] next/image: Removedsquoosh in favor ofsharp as an optional dependency (PR)
• [Breaking] next/image: Changed defaultContent-Disposition toattachment (PR)
• [Breaking] next/image: Error whensrc has leading or trailing spaces (PR)
• [Breaking] Middleware: Applyreact-server condition to limit unrecommended React API imports (PR)
• [Breaking] next/font: Removed support for external@next/font package (PR)
• [Breaking] next/font: Removedfont-family hashing (PR)
• [Breaking] Caching:force-dynamic will now set ano-store default to the fetch cache (PR)
• [Breaking] Config: EnableswcMinify (PR),missingSuspenseWithCSRBailout (PR), andoutputFileTracing (PR) behavior by default and remove deprecated options
• [Breaking] Remove auto-instrumentation for Speed Insights (must now use the dedicated@vercel/speed-insights package) (PR)
• [Breaking] Remove.xml extension for dynamic sitemap routes and align sitemap URLs between development and production (PR)
• [Breaking] We've deprecated exportingexport const runtime = "experimental-edge" in the App Router. Users should now switch toexport const runtime = "edge". We've added acodemod to perform this (PR)
• [Breaking] CallingrevalidateTag andrevalidatePath during render will now throw an error (PR)
• [Breaking] Theinstrumentation.js andmiddleware.js files will now use the vendored React packages (PR)
• [Breaking] The minimum required Node.js version has been updated to 18.18.0 (PR)
• [Breaking]next/dynamic: the deprecatedsuspense prop has been removed and when the component is used in the App Router, it won't insert an empty Suspense boundary anymore (PR)
• [Breaking] When resolving modules on the Edge Runtime, theworker module condition will not be applied (PR)
• [Breaking] Disallow usingssr: false option withnext/dynamic in Server Components (PR)
• [Improvement] Metadata: Updated environment variable fallbacks formetadataBase when hosted on Vercel (PR)
• [Improvement] Fix tree-shaking with mixed namespace and named imports fromoptimizePackageImports (PR)
• [Improvement] Parallel Routes: Provide unmatched catch-all routes with all known params (PR)
• [Improvement] ConfigbundlePagesExternals is now stable and renamed tobundlePagesRouterDependencies
• [Improvement] ConfigserverComponentsExternalPackages is now stable and renamed toserverExternalPackages
• [Improvement] create-next-app: New projects ignore all.env files by default (PR)
• [Improvement] TheoutputFileTracingRoot,outputFileTracingIncludes andoutputFileTracingExcludes have been upgraded from experimental and are now stable (PR)
• [Improvement] Avoid merging global CSS files with CSS module files deeper in the tree (PR)
• [Improvement] The cache handler can be specified via theNEXT_CACHE_HANDLER_PATH environment variable (PR)
• [Improvement] The Pages Router now supports both React 18 and React 19 (PR)
• [Improvement] The Error Overlay now displays a button to copy the Node.js Inspector URL if the inspector is enabled (PR)
• [Improvement] Client prefetches on the App Router now use thepriority attribute (PR)
• [Improvement] Next.js now provides anunstable_rethrow function to rethrow Next.js internal errors in the App Router (PR)
• [Improvement]unstable_after can now be used in static pages (PR)
• [Improvement] If anext/dynamic component is used during SSR, the chunk will be prefetched (PR)
• [Improvement] TheesmExternals option is now supported on the App Router (PR)
• [Improvement] Theexperimental.allowDevelopmentBuild option can be used to allowNODE_ENV=development withnext build for debugging purposes (PR)
• [Improvement] The Server Action transforms are now disabled in the Pages Router (PR)
• [Improvement] Build workers will now stop the build from hanging when they exit (PR)
• [Improvement] When redirecting from a Server Action, revalidations will now apply correctly (PR)
• [Improvement] Dynamic params are now handled correctly for parallel routes on the Edge Runtime (PR)
• [Improvement] Static pages will now respect staleTime after initial load (PR)
• [Improvement]vercel/og updated with a memory leak fix (PR)
• [Improvement] Patch timings updated to allow usage of packages likemsw for APIs mocking (PR)
• [Improvement] Prerendered pages should use static staleTime (PR)

To learn more, check out theupgrade guide.

Contributors

Next.js is the result of the combined work of over 3,000 individual developers, industry partners like Google and Meta, and our core team at Vercel.This release was brought to you by:

• TheNext.js team:Andrew,Hendrik,Janka,Jiachi,Jimmy,Jiwon,JJ,Josh,Sam,Sebastian,Sebbie,Shu,Wyatt, andZack.
• TheTurbopack team:Alex,Benjamin,Donny,Maia,Niklas,Tim,Tobias, andWill.
• TheNext.js Docs team:Delba,Rich,Ismael, andLee.

Huge thanks to @AbhiShake1, @Aerilym, @AhmedBaset, @AnaTofuZ, @Arindam200, @Arinji2, @ArnaudFavier, @ArnoldVanN, @Auxdible, @B33fb0n3, @Bhavya031, @Bjornnyborg, @BunsDev, @CannonLock, @CrutchTheClutch, @DeepakBalaraman, @DerTimonius, @Develliot, @EffectDoplera, @Ehren12, @Ethan-Arrowood, @FluxCapacitor2, @ForsakenHarmony, @Francoscopic, @Gomah, @GyoHeon, @Hemanshu-Upadhyay, @HristovCodes, @HughHzyb, @IAmKushagraSharma, @IDNK2203, @IGassmann, @ImDR, @IncognitoTGT, @Jaaneek, @JamBalaya56562, @Jeffrey-Zutt, @JohnGemstone, @JoshuaKGoldberg, @Julian-Louis, @Juneezee, @KagamiChan, @Kahitar, @KeisukeNagakawa, @KentoMoriwaki, @Kikobeats, @KonkenBonken, @Kuboczoch, @Lada496, @LichuAcu, @LorisSigrist, @Lsnsh, @Luk-z, @Luluno01, @M-YasirGhaffar, @Maaz-Ahmed007, @Manoj-M-S, @ManuLpz4, @Marukome0743, @MaxLeiter, @MehfoozurRehman, @MildTomato, @MonstraG, @N2D4, @NavidNourani, @Nayeem-XTREME, @Netail, @NilsJacobsen, @Ocheretovich, @OlyaPolya, @PapatMayuri, @PaulAsjes, @PlagueFPS, @ProchaLu, @Pyr33x, @QiuranHu, @RiskyMH, @Sam-Phillemon9493, @Sayakie, @Shruthireddy04, @SouthLink, @Strift, @SukkaW, @Teddir, @Tim-Zj, @TrevorSayre, @Unsleeping, @Willem-Jaap, @a89529294, @abdull-haseeb, @abhi12299, @acdlite, @actopas, @adcichowski, @adiguno, @agadzik, @ah100101, @akazwz, @aktoriukas, @aldosch, @alessiomaffeis, @allanchau, @alpedia0, @amannn, @amikofalvy, @anatoliik-lyft, @anay-208, @andrii-bodnar, @anku255, @ankur-dwivedi, @aralroca, @archanaagivale30, @arlyon, @atik-persei, @avdeev, @baeharam, @balazsorban44, @bangseongbeom, @begalinsaf, @bennettdams, @bewinsnw, @bgw, @blvdmitry, @bobaaaaa, @boris-szl, @bosconian-dynamics, @brekk, @brianshano, @cfrank, @chandanpasunoori, @chentsulin, @chogyejin, @chrisjstott, @christian-bromann, @codeSTACKr, @coderfin, @coltonehrman, @controversial, @coopbri, @creativoma, @crebelskydico, @crutchcorn, @darthmaim, @datner, @davidsa03, @delbaoliveira, @devjiwonchoi, @devnyxie, @dhruv-kaushik, @dineshh-m, @diogocapela, @dnhn, @domdomegg, @domin-mnd, @dvoytenko, @ebCrypto, @ekremkenter, @emmerich, @flybayer, @floriangosse, @forsakenharmony, @francoscopic, @frys, @gabrielrolfsen, @gaojude, @gdborton, @greatvivek11, @gnoff, @guisehn, @GyoHeon, @hamirmahal, @hiro0218, @hirotomoyamada, @housseindjirdeh, @hungdoansy, @huozhi, @hwangstar156, @iampoul, @ianmacartney, @icyJoseph, @ijjk, @imddc, @imranolas, @iscekic, @jantimon, @jaredhan418, @jeanmax1me, @jericopulvera, @jjm2317, @jlbovenzo, @joelhooks, @joeshub, @jonathan-ingram, @jonluca, @jontewks, @joostmeijles, @jophy-ye, @jordienr, @jordyfontoura, @kahlstrm, @karlhorky, @karlkeefer, @kartheesan05, @kdy1, @kenji-webdev, @kevva, @khawajaJunaid, @kidonng, @kiner-tang, @kippmr, @kjac, @kjugi, @kshehadeh, @kutsan, @kwonoj, @kxlow, @leerob, @lforst, @li-jia-nan, @liby, @lonr, @lorensr, @lovell, @lubieowoce, @luciancah, @luismiramirez, @lukahartwig, @lumirlumir, @luojiyin1987, @mamuso, @manovotny, @marlier, @mauroaccornero, @maxhaomh, @mayank1513, @mcnaveen, @md-rejoyan-islam, @mehmetozguldev, @mert-duzgun, @mirasayon, @mischnic, @mknichel, @mobeigi, @molebox, @mratlamwala, @mud-ali, @n-ii-ma, @n1ckoates, @nattui, @nauvalazhar, @neila-a, @neoFinch, @niketchandivade, @nisabmohd, @none23, @notomo, @notrab, @nsams, @nurullah, @okoyecharles, @omahs, @paarthmadan, @pathliving, @pavelglac, @penicillin0, @phryneas, @pkiv, @pnutmath, @qqww08, @r34son, @raeyoung-kim, @remcohaszing, @remorses, @rezamauliadi, @rishabhpoddar, @ronanru, @royalfig, @rubyisrust, @ryan-nauman, @ryohidaka, @ryota-murakami, @s-ekai, @saltcod, @samcx, @samijaber, @sean-rallycry, @sebmarkbage, @shubh73, @shuding, @sirTangale, @sleevezip, @slimbde, @soedirgo, @sokra, @sommeeeer, @sopranopillow, @souporserious, @srkirkland, @steadily-worked, @steveluscher, @stipsan, @styfle, @stylessh, @syi0808, @symant233, @tariknh, @theoludwig, @timfish, @timfuhrmann, @timneutkens, @tknickman, @todor0v, @tokkiyaa, @torresgol10, @tranvanhieu01012002, @txxxxc, @typeofweb, @unflxw, @unstubbable, @versecafe, @vicb, @vkryachko, @wbinnssmith, @webtinax, @weicheng95, @wesbos, @whatisagi, @wiesson, @woutvanderploeg, @wyattjoh, @xiaohanyu, @xixixao, @xugetsu, @yosefbeder, @ypessoa, @ytori, @yunsii, @yurivangeffen, @z0n, @zce, @zhawtof, @zsh77, and @ztanner for helping!