Merge pull request #3 from netlify/ll/readme-config-update

README config updates

Author: sdras

README.md

@@ -1,6 +1,6 @@
 ![Next.js on Netlify Build Plugin](nextonnetlify.png)
 
-# Next on Netlify Build Plugin
+# Next.js Build Plugin
 
 This build plugin is a utility for enabling server-side rendering in Next.js on Netlify. It wraps your application in a tiny compatibility layer, so that pages can use Netlify Functions to be server-side rendered.
 
@@ -24,66 +24,20 @@ This build plugin is a utility for enabling server-side rendering in Next.js on
 
 ## Installation and Configuration
 
-Create a `netlify.toml`:
+1. `npm install netlify-plugin-nextjs`
+
+2. Create a `netlify.toml` in the root of your poject:
 
 ```toml
 [build]
   command   = "npm run build"
   functions = "out_functions"
-  publish   = "out_publish"
-```
-
-## Setup
-
-#### 1. Set Next.js target to serverless
-
-We must build our Next.js app as a serverless app. You can read more about serverless Next.js [here](https://nextjs.org/docs/api-reference/next.config.js/build-target#serverless-target).
+  publish = "out_publish"
 
-It's super simple. Just create a `next.config.js` file and write the following:
-
-```js
-// next.config.js
-
-module.exports = {
-  // Target must be serverless
-  target: "serverless",
-}
+[[plugins]]
+  package = "netlify-plugin-nextjs"
 ```
 
-If binaries are needed in the deployment the following configuration is needed ([Prisma](https://github.com/prisma/prisma) is an example):
-
-```js
-// next.config.js
-
-module.exports = {
-  // Target must be experimental-serverless-trace
-  // Your build time will be longer with this option
-  target: "experimental-serverless-trace",
-}
-```
-
-#### 2. Add postbuild hook
-
-The next-on-netlify package adds the `next-on-netlify` command. When we run this command, some magic happens to prepare our Next.js app for hosting on Netlify\*.
-
-We want the next-on-netlify command to run after we build our NextJS application. So let's add a postbuild hook to our package.json file:
-
-```json
-{
-  "name": "my-nextjs-app",
-  "scripts": {
-    "dev": "next",
-    "build": "next build",
-    "postbuild": "next-on-netlify"
-  },
-  ....
-}
-```
-
-\*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).
-
-We're done. Let's deploy 🚀🚀🚀
-
 ## Optional Extras
 
 #### Preview Locally
@@ -150,10 +104,6 @@ SSR pages and API endpoints. It is currently not possible to create custom Netli
 
 ## Caveats
 
-### Preview Mode
-
-[Next.js 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`
 
 [Fallback pages](https://nextjs.org/docs/basic-features/data-fetching#fallback-true) behave differently with `next-on-netlify` than they do with Next.js. On Next.js, when navigating to a path that is not defined in `getStaticPaths`, it first displays the fallback page. Next.js then generates the HTML in the background and caches it for future requests.