Bump versions of dependencies and Node.js

.nvmrc

@@ -1 +1 @@
-v6.10.3
+v8.10.0

.prettierignore

@@ -1,3 +1,4 @@
 scaffold/
 package.json
 package-lock.json
+snippets/next.js

.travis.yml

@@ -1,8 +1,7 @@
 language: node_js
 node_js:
-  - "6.10.3"
-  - "7"
-  - "8"
+  - "8.10.0"
+  - "10"
 notifications:
   email: false
 deploy:
@@ -11,5 +10,5 @@ deploy:
   api_key: $NPM_TOKEN
   on:
     tags: true
-    node: "6.10.3"
+    node: "8.10.0"
   skip_cleanup: true

README-source.md

@@ -1179,7 +1179,7 @@ This makes it pretty straightforward to integrate into your testing interface. I
 ```yaml
 language: node_js
 node_js:
-  - "6.10.2"
+  - "LAMBDA_VERSION"
 before_script: npm install -g zapier-platform-cli
 script: CLIENT_ID=1234 CLIENT_SECRET=abcd zapier test
 ```

README.md

@@ -156,16 +156,16 @@ From a user perspective, both the CLI and the existing web builder platform offe
 
 ### Requirements
 
-All Zapier CLI apps are run using Node.js `v6.10.3`.
+All Zapier CLI apps are run using Node.js `v8.10.0`.
 
-You can develop using any version of Node you'd like, but your eventual code must be compatible with `v6.10.3`. If you're using features not yet available in `v6.10.3`, you can transpile your code to a compatible format with [Babel](https://babeljs.io/) (or similar).
+You can develop using any version of Node you'd like, but your eventual code must be compatible with `v8.10.0`. If you're using features not yet available in `v8.10.0`, you can transpile your code to a compatible format with [Babel](https://babeljs.io/) (or similar).
 
-To ensure stability for our users, we strongly encourage you run tests on `v6.10.3` sometime before your code reaches users. This can be done multiple ways.
+To ensure stability for our users, we strongly encourage you run tests on `v8.10.0` sometime before your code reaches users. This can be done multiple ways.
 
 Firstly, by using a CI tool (like [Travis CI](https://travis-ci.org/) or [Circle CI](https://circleci.com/), which are free for open source projects). We provide a sample [.travis.yml](https://github.com/zapier/zapier-platform-example-app-minimal/blob/master/.travis.yml) file in our template apps to get you started.
 
 Alternatively, you can change your local node version with tools such as [nvm](https://github.com/creationix/nvm#installation) or [n](https://github.com/tj/n#installation).
-Then you can either swap to that version with `nvm use v6.10.3`, or do `nvm exec v6.10.3 zapier test` so you can run tests without having to switch versions while developing.
+Then you can either swap to that version with `nvm use v8.10.0`, or do `nvm exec v8.10.0 zapier test` so you can run tests without having to switch versions while developing.
 
 
 ### Quick Setup Guide
@@ -2071,7 +2071,7 @@ This makes it pretty straightforward to integrate into your testing interface. I
 ```yaml
 language: node_js
 node_js:
-  - "6.10.2"
+  - "8.10.0"
 before_script: npm install -g zapier-platform-cli
 script: CLIENT_ID=1234 CLIENT_SECRET=abcd zapier test
 ```
@@ -2160,7 +2160,7 @@ See [the wiki](https://github.com/zapier/zapier-platform-cli/wiki/Example-Apps)
 
 ### Why doesn't Zapier support newer versions of Node.js?
 
-We run your code on AWS Lambda, which only supports a few [versions](https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html) of Node (the latest of which is `v6.10.3`. As that updates, so too will we.
+We run your code on AWS Lambda, which only supports a few [versions](https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html) of Node (the latest of which is `v8.10.0`. As that updates, so too will we.
 
 ### How do I manually set the Node.js version to run my app with?
 

docs/index.html

@@ -667,8 +667,8 @@ <h3 id="requirements">Requirements</h3>
 </div><div class="row">
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
-      <p>All Zapier CLI apps are run using Node.js <code>v6.10.3</code>.</p><p>You can develop using any version of Node you&apos;d like, but your eventual code must be compatible with <code>v6.10.3</code>. If you&apos;re using features not yet available in <code>v6.10.3</code>, you can transpile your code to a compatible format with <a href="https://babeljs.io/">Babel</a> (or similar).</p><p>To ensure stability for our users, we strongly encourage you run tests on <code>v6.10.3</code> sometime before your code reaches users. This can be done multiple ways.</p><p>Firstly, by using a CI tool (like <a href="https://travis-ci.org/">Travis CI</a> or <a href="https://circleci.com/">Circle CI</a>, which are free for open source projects). We provide a sample <a href="https://github.com/zapier/zapier-platform-example-app-minimal/blob/master/.travis.yml">.travis.yml</a> file in our template apps to get you started.</p><p>Alternatively, you can change your local node version with tools such as <a href="https://github.com/creationix/nvm#installation">nvm</a> or <a href="https://github.com/tj/n#installation">n</a>.
-Then you can either swap to that version with <code>nvm use v6.10.3</code>, or do <code>nvm exec v6.10.3 zapier test</code> so you can run tests without having to switch versions while developing.</p>
+      <p>All Zapier CLI apps are run using Node.js <code>v8.10.0</code>.</p><p>You can develop using any version of Node you&apos;d like, but your eventual code must be compatible with <code>v8.10.0</code>. If you&apos;re using features not yet available in <code>v8.10.0</code>, you can transpile your code to a compatible format with <a href="https://babeljs.io/">Babel</a> (or similar).</p><p>To ensure stability for our users, we strongly encourage you run tests on <code>v8.10.0</code> sometime before your code reaches users. This can be done multiple ways.</p><p>Firstly, by using a CI tool (like <a href="https://travis-ci.org/">Travis CI</a> or <a href="https://circleci.com/">Circle CI</a>, which are free for open source projects). We provide a sample <a href="https://github.com/zapier/zapier-platform-example-app-minimal/blob/master/.travis.yml">.travis.yml</a> file in our template apps to get you started.</p><p>Alternatively, you can change your local node version with tools such as <a href="https://github.com/creationix/nvm#installation">nvm</a> or <a href="https://github.com/tj/n#installation">n</a>.
+Then you can either swap to that version with <code>nvm use v8.10.0</code>, or do <code>nvm exec v8.10.0 zapier test</code> so you can run tests without having to switch versions while developing.</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height is-empty docs-code">
 
@@ -3667,7 +3667,7 @@ <h3 id="testing-in-your-ci">Testing in Your CI</h3>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
       <pre><code class="lang-yaml"><span class="hljs-attr">language:</span> <span class="hljs-string">node_js</span>
 <span class="hljs-attr">node_js:</span>
-<span class="hljs-bullet">  -</span> <span class="hljs-string">&quot;6.10.2&quot;</span>
+<span class="hljs-bullet">  -</span> <span class="hljs-string">&quot;8.10.0&quot;</span>
 <span class="hljs-attr">before_script:</span> <span class="hljs-string">npm</span> <span class="hljs-string">install</span> <span class="hljs-bullet">-g</span> <span class="hljs-string">zapier-platform-cli</span>
 <span class="hljs-attr">script:</span> <span class="hljs-string">CLIENT_ID=1234</span> <span class="hljs-string">CLIENT_SECRET=abcd</span> <span class="hljs-string">zapier</span> <span class="hljs-string">test</span>
 </code></pre>
@@ -3845,7 +3845,7 @@ <h3 id="why-doesnt-zapier-support-newer-versions-of-nodejs">Why doesn&apos;t Zap
 </div><div class="row">
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
-      <p>We run your code on AWS Lambda, which only supports a few <a href="https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html">versions</a> of Node (the latest of which is <code>v6.10.3</code>. As that updates, so too will we.</p>
+      <p>We run your code on AWS Lambda, which only supports a few <a href="https://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions.html">versions</a> of Node (the latest of which is <code>v8.10.0</code>. As that updates, so too will we.</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height is-empty docs-code">