upgrade NoN to 2.8.1 and explain CLI usage workflow in README

Author: lindsaylevine

README.md

@@ -16,6 +16,7 @@ This build plugin is a utility for supporting Next.js on Netlify. To enable serv
 ## Table of Contents
 
 - [Installation and Configuration](#installation-and-configuration)
+- [CLI Usage](#cli-usage)
 - [Custom Netlify Functions](#custom-netlify-functions)
 - [Publish Directory](#publish-directory)
 - [Custom Netlify Redirects](#custom-netlify-redirects)
@@ -40,7 +41,7 @@ Read more about [UI-based plugin installation](https://docs.netlify.com/configur
     ```toml
     [build]
       command   = "npm run build"
-    
+
     [[plugins]]
       package = "@netlify/plugin-nextjs"
     ```
@@ -51,14 +52,29 @@ Read more about [UI-based plugin installation](https://docs.netlify.com/configur
     npm install -D @netlify/plugin-nextjs
     ```
 
-    or 
+    or
 
     ```
     yarn add -D @netlify/plugin-nextjs
     ```
 
 Read more about [file-based plugin installation](https://docs.netlify.com/configure-builds/build-plugins/#file-based-installation) in our docs.
 
+## CLI Usage
+
+If you'd like to build and deploy your project using the [Netlify CLI](https://docs.netlify.com/cli/get-started/), we recommend this workflow to manage git tracking plugin-generated files:
+
+1. Make sure all your project's files are committed before running a build with the CLI
+2. Run any number of builds and deploys freely (i.e. `netlify build`, `netlify deploy --build`, `netlify deploy --prod`)
+3. Run `git stash --include-unstaged` to easily ignore plugin-generated files
+
+Plugin-generated files will output into either (a) the default functions and publish directories (`netlify-automatic-functions` and `.`, respectively) or (b) whichever custom functions and publish directories you configure. See below for custom directory configuration. It's important to note that, in both cases (a) and (b), the CLI may mix your project's source code and plugin-generated files; this is why we recommend committing all project source files before running CLI builds.
+
+**Debugging CLI builds:**
+- If you're seeing a `{FILE_NAME} already exists` error running a CLI build, this may be because your `node_modules` got purged between builds or because of lingering unstashed files from outdated builds. To resolve, you need to manually remove any plugin-generated files from your project directory.
+
+We're looking to improve the CLI experience to avoid this manual cleanup and git management! Feel free to open an issue to report feedback on the CLI experience.
+
 ## Custom Netlify Functions
 
 This plugin creates one Netlify Function for each Next.js page that requires one.
@@ -107,10 +123,6 @@ Read more about [Netlify redirects](https://docs.netlify.com/routing/redirects/)
 
 You can check our `package.json` for supported Next and Node versions. Our support of Next 10 is currently experimental.
 
-### CLI
-
-This plugin is currently not stable for use with the Netlify CLI. Support for the plugin is in development.
-
 ### Fallbacks for Pages with `getStaticPaths`
 
 [Fallback pages](https://nextjs.org/docs/basic-features/data-fetching#fallback-true) behave differently with this plugin 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.