Replace /FinnWoelm/next-on-netlify with /netlify/next-on-netlify

Replace all links to the old GitHub repository under FinnWoelm with the
links to the new GitHub repository under netlify.

Author: FinnWoelm

CHANGELOG.md

@@ -6,38 +6,38 @@
 
 ## 2.3.1 (2020-07-19)
 
-- Fix: Correctly get distDir from `next.config.js` when config is a function ([#25](https://github.com/FinnWoelm/next-on-netlify/issues/25))
+- Fix: Correctly get distDir from `next.config.js` when config is a function ([#25](https://github.com/netlify/next-on-netlify/issues/25))
 
 ## 2.3.0 (2020-06-26)
 
-- Add support for [NextJS Preview Mode](https://nextjs.org/docs/advanced-features/preview-mode) ([#10](https://github.com/FinnWoelm/next-on-netlify/issues/10))
+- Add support for [NextJS Preview Mode](https://nextjs.org/docs/advanced-features/preview-mode) ([#10](https://github.com/netlify/next-on-netlify/issues/10))
 
   Note: NextJS Preview Mode does not work on pages that are pre-rendered (pages with `getStaticProps`). Netlify currently does not support cookie-based redirects, which are needed for supporting preview mode on pre-rendered pages. Preview mode works correctly on any server-side-rendered pages (pages with `getInitialProps` or `getServerSideProps`).
 
 - Use `multiValueHeaders` in Netlify Functions for incoming requests and for outgoing responses. This offers many benefits over plain `headers`, such as setting multiple cookies within one response.
 
 ## 2.2.0 (2020-06-22)
 
-- Add support for defining custom redirects in a `_redirects` file at the project root directory. Unlike redirects specified in your `netlify.toml` file, the redirects from the `_redirects` file take precedence over those generated by `next-on-netlify` ([#21](https://github.com/FinnWoelm/next-on-netlify/pull/21))
+- Add support for defining custom redirects in a `_redirects` file at the project root directory. Unlike redirects specified in your `netlify.toml` file, the redirects from the `_redirects` file take precedence over those generated by `next-on-netlify` ([#21](https://github.com/netlify/next-on-netlify/pull/21))
 
 ## 2.1.0 (2020-06-14)
 
-- Add support for [NextJS optional catch-all routes](https://nextjs.org/docs/api-routes/dynamic-api-routes#optional-catch-all-api-routes) ([#15](https://github.com/FinnWoelm/next-on-netlify/pull/15))
-- Fix: An `index.js` page with `getStaticProps` no longer causes `next-on-netlify` to fail ([#18](https://github.com/FinnWoelm/next-on-netlify/pull/18))
-- Fix: Catch-all routes now correctly require that at least one URL parameter is present (unlike optional catch-all routes) ([479b7e7](https://github.com/FinnWoelm/next-on-netlify/commit/479b7e73f1a11778eb5ef66ded02aa1c17e38697))
-- Fix: Data routes now correctly work for pages with catch-all routing ([0412b45](https://github.com/FinnWoelm/next-on-netlify/commit/0412b45fe3917a082be563c1720e85cf3affd4e1))
+- Add support for [NextJS optional catch-all routes](https://nextjs.org/docs/api-routes/dynamic-api-routes#optional-catch-all-api-routes) ([#15](https://github.com/netlify/next-on-netlify/pull/15))
+- Fix: An `index.js` page with `getStaticProps` no longer causes `next-on-netlify` to fail ([#18](https://github.com/netlify/next-on-netlify/pull/18))
+- Fix: Catch-all routes now correctly require that at least one URL parameter is present (unlike optional catch-all routes) ([479b7e7](https://github.com/netlify/next-on-netlify/commit/479b7e73f1a11778eb5ef66ded02aa1c17e38697))
+- Fix: Data routes now correctly work for pages with catch-all routing ([0412b45](https://github.com/netlify/next-on-netlify/commit/0412b45fe3917a082be563c1720e85cf3affd4e1))
 
 ## 2.0.0 (2020-06-02)
 
-- **Breaking: You must change your `netlify.toml` configuration for next-on-netlify v2.0.0.** Please [look at the README](https://github.com/FinnWoelm/next-on-netlify#3-configure-netlify) for the latest configuration.  
+- **Breaking: You must change your `netlify.toml` configuration for next-on-netlify v2.0.0.** Please [look at the README](https://github.com/netlify/next-on-netlify#3-configure-netlify) for the latest configuration.  
 `next-on-netlify` now builds pre-rendered pages and static assets in `out_publish`. Netlify Functions for SSR pages are built to `out_functions`.
-- Add support for `getStaticProps` ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
-- Add support for `getStaticPaths` with and without fallback ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
-- Add support for `getServerSideProps` ([#7](https://github.com/FinnWoelm/next-on-netlify/issues/7))
-- Query string parameters are now correctly passed to Next Pages and API endpoints ([#9](https://github.com/FinnWoelm/next-on-netlify/issues/9))
-- Response headers are now correctly set ([#9](https://github.com/FinnWoelm/next-on-netlify/issues/9#issuecomment-633288179))
+- Add support for `getStaticProps` ([#7](https://github.com/netlify/next-on-netlify/issues/7))
+- Add support for `getStaticPaths` with and without fallback ([#7](https://github.com/netlify/next-on-netlify/issues/7))
+- Add support for `getServerSideProps` ([#7](https://github.com/netlify/next-on-netlify/issues/7))
+- Query string parameters are now correctly passed to Next Pages and API endpoints ([#9](https://github.com/netlify/next-on-netlify/issues/9))
+- Response headers are now correctly set ([#9](https://github.com/netlify/next-on-netlify/issues/9#issuecomment-633288179))
 - When a user encounters a 404, `next-on-netlify` now display the NextJS 404 page rather than Netlify's default 404 page. You can [customize the NextJS 404 page](https://nextjs.org/docs/advanced-features/custom-error-page#customizing-the-404-page).
- ([#2](https://github.com/FinnWoelm/next-on-netlify/issues/2))
+ ([#2](https://github.com/netlify/next-on-netlify/issues/2))
 - Every page with server-side rendering is now converted to a stand-alone Netlify Function. Previously, all SSR pages were bundled in a single Netlify Function.
 - `next-on-netlify` now prints out which pages are being converted to Netlify Functions for SSR, which pages are served as pre-rendered HTML, and the redirects that are being generated.
 - Adding custom redirects via a `_redirects` file in the project root is no longer supported. Let me know if you want this back. Or define your redirects in `netlify.toml`.
@@ -50,7 +50,7 @@
 
 ## 1.1.0 (2020-04-19)
 
-- Add support for catch-all routes ([#1](https://github.com/FinnWoelm/next-on-netlify/pull/1), [#5](https://github.com/FinnWoelm/next-on-netlify/pull/5))
+- Add support for catch-all routes ([#1](https://github.com/netlify/next-on-netlify/pull/1), [#5](https://github.com/netlify/next-on-netlify/pull/5))
 - README: Fix instructions for local preview
 
 ## 1.0.1 (2020-01-27)

README.md

@@ -15,7 +15,7 @@ Principal Developer Experience Engineer at Netlify, will be joining
 # README
 
 [![NPM version](https://img.shields.io/npm/v/next-on-netlify)](https://www.npmjs.com/package/next-on-netlify)
-[![MIT license](https://img.shields.io/npm/l/next-on-netlify)](https://github.com/FinnWoelm/next-on-netlify/blob/master/LICENSE)
+[![MIT license](https://img.shields.io/npm/l/next-on-netlify)](https://github.com/netlify/next-on-netlify/blob/master/LICENSE)
 [![NPM downloads](https://img.shields.io/npm/dt/next-on-netlify)](https://www.npmjs.com/package/next-on-netlify)
 [![Tested with Cypress.io](https://img.shields.io/badge/tested%20with-Cypress-04C38E.svg)](https://www.cypress.io/)
 
@@ -81,7 +81,7 @@ We want the next-on-netlify command to run after we build our NextJS application
 }
 ```
 
-\*If you're curious about the "magic", check out the well-documented [`next-on-netlify.js` file](https://github.com/FinnWoelm/next-on-netlify/blob/master/next-on-netlify.js).
+\*If you're curious about the "magic", check out the well-documented [`next-on-netlify.js` file](https://github.com/netlify/next-on-netlify/blob/master/next-on-netlify.js).
 
 #### 3. Configure Netlify
 
@@ -104,7 +104,7 @@ I recommend you still use `next dev` to build and preview your application local
 
 But if you want to emulate the Netlify deployment on your computer, you can also run `next-on-netlify` locally and then use `netlify-cli` to preview the result.
 
-First, install the latest version of `netlify-cli` (you can also [look at package.json](https://github.com/FinnWoelm/next-on-netlify/blob/master/package.json) to see the version against which next-on-netlify has been tested):
+First, install the latest version of `netlify-cli` (you can also [look at package.json](https://github.com/netlify/next-on-netlify/blob/master/package.json) to see the version against which next-on-netlify has been tested):
 
 ```bash
 npm install -g netlify-cli
@@ -163,7 +163,7 @@ SSR pages and API endpoints. It is currently not possible to create custom Netli
 
 ### Preview Mode
 
-[NextJS Preview Mode](https://nextjs.org/docs/advanced-features/preview-mode) does not work on pages that are pre-rendered (pages with `getStaticProps`). Netlify currently does not support cookie-based redirects, which are needed for supporting preview mode on pre-rendered pages. Preview mode works correctly on any server-side-rendered pages (pages with `getInitialProps` or `getServerSideProps`). See: [Issue #10](https://github.com/FinnWoelm/next-on-netlify/issues/10)
+[NextJS Preview Mode](https://nextjs.org/docs/advanced-features/preview-mode) does not work on pages that are pre-rendered (pages with `getStaticProps`). Netlify currently does not support cookie-based redirects, which are needed for supporting preview mode on pre-rendered pages. Preview mode works correctly on any server-side-rendered pages (pages with `getInitialProps` or `getServerSideProps`). See: [Issue #10](https://github.com/netlify/next-on-netlify/issues/10)
 
 
 ### Fallbacks for Pages with `getStaticPaths`
@@ -172,14 +172,14 @@ SSR pages and API endpoints. It is currently not possible to create custom Netli
 
 With `next-on-netlify`, when navigating to a path that is not defined in `getStaticPaths`, it server-side renders the page and sends it directly to the user. The user never sees the fallback page. The page is not cached for future requests.
 
-For more on this, see: [Issue #7](https://github.com/FinnWoelm/next-on-netlify/issues/7#issuecomment-636883539)
+For more on this, see: [Issue #7](https://github.com/netlify/next-on-netlify/issues/7#issuecomment-636883539)
 
 ## Showcase
 
 The following sites are built with `next-on-netlify`:
 
-![missionbit.org](https://raw.githubusercontent.com/FinnWoelm/next-on-netlify/master/assets/showcase-missionbit.png)  
-[missionbit.org](https://www.missionbit.org/) ([#18](https://github.com/FinnWoelm/next-on-netlify/pull/18#issuecomment-643828966))
+![missionbit.org](https://raw.githubusercontent.com/netlify/next-on-netlify/master/assets/showcase-missionbit.png)  
+[missionbit.org](https://www.missionbit.org/) ([#18](https://github.com/netlify/next-on-netlify/pull/18#issuecomment-643828966))
 
 Are you building something awesome with `next-on-netlify`? 🔥 Let me know and we will feature it here :)
 

package.json

@@ -16,9 +16,9 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/FinnWoelm/next-on-netlify"
+    "url": "https://github.com/netlify/next-on-netlify"
   },
-  "homepage": "https://github.com/FinnWoelm/next-on-netlify",
+  "homepage": "https://github.com/netlify/next-on-netlify",
   "author": "Finn Woelm",
   "license": "MIT",
   "files": [

tests/nextConfigFunction.test.js

@@ -1,5 +1,5 @@
 // Test next-on-netlify when config is set from a function in next.config.js
-// See: https://github.com/FinnWoelm/next-on-netlify/issues/25
+// See: https://github.com/netlify/next-on-netlify/issues/25
 const { parse, join } = require('path')
 const { copySync, emptyDirSync, existsSync,
         readdirSync, readFileSync, readJsonSync } = require('fs-extra')

tests/optionalCatchAll.test.js

@@ -1,5 +1,5 @@
 // Test that next-on-netlify does not crash when pre-rendering index.js file.
-// See: https://github.com/FinnWoelm/next-on-netlify/issues/2#issuecomment-636415494
+// See: https://github.com/netlify/next-on-netlify/issues/2#issuecomment-636415494
 
 const { parse, join } = require('path')
 const { copySync, emptyDirSync, existsSync,

tests/preRenderedIndexPages.test.js

@@ -1,5 +1,5 @@
 // Test that next-on-netlify does not crash when pre-rendering index.js file.
-// See: https://github.com/FinnWoelm/next-on-netlify/issues/2#issuecomment-636415494
+// See: https://github.com/netlify/next-on-netlify/issues/2#issuecomment-636415494
 
 const { parse, join } = require('path')
 const { copySync, emptyDirSync, existsSync,