Publish Stable

- @vercel/frameworks@0.0.14
 - @vercel/build-utils@2.3.0
 - @vercel/cgi@1.0.5
 - vercel@19.0.0
 - @vercel/client@8.0.0
 - @vercel/go@1.1.0
 - @vercel/next@2.6.0
 - @vercel/node-bridge@1.3.0
 - @vercel/node@1.6.0
 - @vercel/python@1.2.0
 - @vercel/routing-utils@1.8.2
 - @vercel/ruby@1.2.0
 - @vercel/static-build@0.17.0

.gitattributes

@@ -1,5 +1,8 @@
 # Ignore test fixtures in GitHub Languages
 # See https://github.com/github/linguist#vendored-code
+examples/* linguist-vendored
+utils/* linguist-vendored
+test/* linguist-vendored
 packages/*/test/* linguist-vendored
 
 # Go build fails with Windows line endings.

.github/CODE_OF_CONDUCT.md

@@ -55,7 +55,7 @@ further defined and clarified by project maintainers.
 ### Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at [abuse@zeit.co](mailto:abuse@zeit.co). All
+reported by contacting the project team at [coc@vercel.com](mailto:coc@vercel.com). All
 complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.

.github/CONTRIBUTING.md

@@ -47,7 +47,7 @@ Unit tests are run locally with `jest` and execute quickly because they are test
 
 ### Integration tests
 
-Integration tests create deployments to your ZEIT account using the `test` project name. After each test is deployed, the `probes` key is used to check if the response is the expected value. If the value doesn't match, you'll see a message explaining the difference. If the deployment failed to build, you'll see a more generic message like the following:
+Integration tests create deployments to your Vercel account using the `test` project name. After each test is deployed, the `probes` key is used to check if the response is the expected value. If the value doesn't match, you'll see a message explaining the difference. If the deployment failed to build, you'll see a more generic message like the following:
 
 ```
 [Error: Fetched page https://test-8ashcdlew.now.sh/root.js does not contain hello Root!. Instead it contains An error occurred with this application.
@@ -92,7 +92,7 @@ Sometimes you want to test changes to a Builder against an existing project, may
 2. Run `yarn build` to compile typescript and other build steps
 3. Run `npm pack` to create a tarball file
 4. Run `now *.tgz` to upload the tarball file and get a URL
-5. Edit any existing `now.json` project and replace `use` with the URL
+5. Edit any existing `vercel.json` project and replace `use` with the URL
 6. Run `now` or `now dev` to deploy with the experimental Builder
 
 ## Add a New Framework
@@ -102,4 +102,4 @@ You can add support for a new Framework by creating a Pull Request for this repo
 1. Add the Framework to the `@now/frameworks` package: The file is located in `packages/frameworks/frameworks.json`. You can copy the structure of an existing one and adjust the required fields. Note that the `settings` property either contains a `value` or a `placeholder`. The `value` property is used when something is not configurable, the `placeholder` is used when something is configurable and can be changed with configuration. An example would be the Output Directory for Hugo, it's `public` by default but can be changed through its config file, so we use `placeholder` with an explanation of what can be used.
 2. Add an example to the `examples/` directory: The name of the directory should equal the slug of the framework used in `@now/frameworks`. The `.github/EXAMPLE_README_TEMPLATE.md` file can be used to create a `README.md` file for the example.
 3. Update the `@now/static-build` package: The file `packages/now-static-build/src/frameworks.ts` has to be extended. You can add default routes that will always be applied to projects that use this Framework or specify some paths that will be cached to speed up the build process.
-4. After your Pull Request has been merged and released, other users can select the example on the ZEIT Now dashboard and deploy it.
+4. After your Pull Request has been merged and released, other users can select the example on the Vercel dashboard and deploy it.

.github/EXAMPLE_README_TEMPLATE.md

@@ -1,16 +1,16 @@
 # [Name] Example
 
-This directory is a brief example of a [Name](site-link) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Name](site-link) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own [Name] project with ZEIT Now.
+Deploy your own [Name] project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now-examples/tree/master/example-directory)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now-examples/tree/master/example-directory)
 
 ### How We Created This Example
 
-To get started with [Name] on Now, you can use the [CLI Tool Used](CLI-link) to initialize the project:
+To get started with [Name] on Vercel, you can use the [CLI Tool Used](CLI-link) to initialize the project:
 
 ```shell
 $ now init charge

.github/ISSUE_TEMPLATE/config.yml

@@ -1,8 +1,8 @@
 blank_issues_enabled: false
 contact_links:
   - name: Bug Report
-    url: https://zeit.co/support/request
-    about: Report a bug using the ZEIT Now support form
+    url: https://vercel.com/support/request
+    about: Report a bug using the Vercel support form
   - name: Feature Request
     url: https://github.com/zeit/now/discussions/new
     about: Request a feature to be added to the platform

.github/workflows/cancel.yml

@@ -2,7 +2,7 @@ name: Cancel
 on:
   push:
     branches:
-    - '*'
+    - '**'
     - '!master'
 
 jobs:

.github/workflows/test-integration-cli.yml

@@ -22,9 +22,6 @@ jobs:
       - uses: actions/checkout@v2
       - run: git fetch origin master --depth=10
       - run: git fetch origin ${{ github.ref }} --depth=10
-      - name: Install Hugo
-        if: matrix.os == 'macos-latest'
-        run: curl -L -O https://github.com/gohugoio/hugo/releases/download/v0.56.0/hugo_0.56.0_macOS-64bit.tar.gz && tar -xzf hugo_0.56.0_macOS-64bit.tar.gz && mv ./hugo packages/now-cli/test/dev/fixtures/08-hugo/
       - run: yarn install
       - run: yarn run build
       - uses: actions/setup-node@v1

.github/workflows/test-integration-dev.yml

@@ -11,7 +11,7 @@ on:
 jobs:
   test:
     name: Dev
-    timeout-minutes: 30
+    timeout-minutes: 45
     strategy:
       fail-fast: false
       matrix:
@@ -31,3 +31,6 @@ jobs:
         with:
           node-version: ${{ matrix.node }}
       - run: yarn test-integration-dev --clean false
+        env:
+          ZEIT_TEAM_TOKEN: ${{ secrets.ZEIT_TEAM_TOKEN }}
+          ZEIT_REGISTRATION_URL: ${{ secrets.ZEIT_REGISTRATION_URL }}

.github/workflows/test-unit.yml

@@ -25,9 +25,10 @@ jobs:
       - uses: actions/setup-node@v1
       - run: yarn install
       - run: yarn run build
-      - run: yarn run test-lint
+      - run: yarn run lint
+        if: matrix.os == 'ubuntu-latest' && matrix.node == 12 # only run lint once
       - run: yarn run test-unit --clean false
-      - run: yarn workspace now run coverage
-        if: matrix.os == 'ubuntu-latest' && matrix.node == 12 # only run once
+      - run: yarn workspace vercel run coverage
+        if: matrix.os == 'ubuntu-latest' && matrix.node == 12 # only run coverage once
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.gitignore

@@ -6,6 +6,7 @@ npm-debug.log
 yarn-error.log
 .nyc_output
 coverage
+coverage.lcov
 *.swp
 *.bak
 *.tgz
@@ -19,9 +20,12 @@ packages/now-cli/test/**/node_modules
 packages/now-cli/test/dev/fixtures/08-hugo/hugo
 packages/now-cli/test/dev/fixtures/**/dist
 packages/now-cli/test/dev/fixtures/**/public
+packages/now-cli/test/dev/fixtures/**/.now
+packages/now-cli/test/dev/fixtures/**/.vercel
 packages/now-cli/test/fixtures/integration
 test/lib/deployment/failed-page.txt
 .DS_Store
 .next
-.env
-public
+/.env
+/public
+__pycache__

DEVELOPING_A_RUNTIME.md

@@ -3,10 +3,10 @@
 The following page is a reference for how to create a Runtime using the available Runtime API.
 
 A Runtime is an npm module that exposes a `build` function and optionally an `analyze` function and `prepareCache` function.
-Official Runtimes are published to [npmjs.com](https://npmjs.com) as a package and referenced in the `use` property of the `now.json` configuration file.
+Official Runtimes are published to [npmjs.com](https://npmjs.com) as a package and referenced in the `use` property of the `vercel.json` configuration file.
 However, the `use` property will work with any [npm install argument](https://docs.npmjs.com/cli/install) such as a git repo url which is useful for testing your Runtime.
 
-See the [Runtimes Documentation](https://zeit.co/docs/runtimes) to view example usage.
+See the [Runtimes Documentation](https://vercel.com/docs/runtimes) to view example usage.
 
 ## Runtime Exports
 
@@ -18,7 +18,7 @@ The latest and suggested version is `3`.
 
 ### `analyze`
 
-An **optional** exported function that returns a unique fingerprint used for the purpose of [build de-duplication](https://zeit.co/docs/v2/advanced/concepts/immutability#deduplication-algorithm). If the `analyze` function is not supplied, a random fingerprint is assigned to each build.
+An **optional** exported function that returns a unique fingerprint used for the purpose of [build de-duplication](https://vercel.com/docs/v2/platform/deployments#deduplication). If the `analyze` function is not supplied, a random fingerprint is assigned to each build.
 
 ```js
 export analyze({
@@ -43,7 +43,7 @@ export analyze(options: AnalyzeOptions) {
 
 A **required** exported function that returns a [Serverless Function](#serverless-function).
 
-What's a Serverless Function? Read about [Serverless Function concepts](https://zeit.co/docs/v2/deployments/concepts/lambdas) to learn more.
+What's a Serverless Function? Read about [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction) to learn more.
 
 ```js
 build({
@@ -109,7 +109,7 @@ export prepareCache(options: PrepareCacheOptions) {
 
 ### `shouldServe`
 
-An **optional** exported function that is only used by `now dev` in [Now CLI](https:///download) and indicates whether a [Runtime](https://zeit.co/docs/v2/advanced/runtimes) wants to be responsible for building a certain request path.
+An **optional** exported function that is only used by `now dev` in [Now CLI](https:///download) and indicates whether a [Runtime](https://vercel.com/docs/runtimes) wants to be responsible for building a certain request path.
 
 ```js
 shouldServe({
@@ -143,7 +143,7 @@ The exported functions [`analyze`](#analyze), [`build`](#build), and [`prepareCa
 - `entrypoint`: Name of entrypoint file for this particular build job. Value `files[entrypoint]` is guaranteed to exist and be a valid [File](#files) reference. `entrypoint` is always a discrete file and never a glob, since globs are expanded into separate builds at deployment time.
 - `workPath`: A writable temporary directory where you are encouraged to perform your build process. This directory will be populated with the restored cache from the previous run (if any) for [`analyze`](#analyze) and [`build`](#build).
 - `cachePath`: A writable temporary directory where you can build a cache for the next run. This is only passed to `prepareCache`.
-- `config`: An arbitrary object passed from by the user in the [Build definition](#defining-the-build-step) in `now.json`.
+- `config`: An arbitrary object passed from by the user in the [Build definition](#defining-the-build-step) in `vercel.json`.
 
 ## Examples
 
@@ -153,7 +153,7 @@ Check out our [Node.js Runtime](https://github.com/zeit/now/tree/master/packages
 
 ### Execution Context
 
-A [Serverless Function](https://zeit.co/docs/v2/advanced/concepts/lambdas) is created where the Runtime logic is executed. The lambda is run using the Node.js 8 runtime. A brand new sandbox is created for each deployment, for security reasons. The sandbox is cleaned up between executions to ensure no lingering temporary files are shared from build to build.
+A [Serverless Function](https://vercel.com/docs/v2/serverless-functions/introduction) is created where the Runtime logic is executed. The lambda is run using the Node.js 8 runtime. A brand new sandbox is created for each deployment, for security reasons. The sandbox is cleaned up between executions to ensure no lingering temporary files are shared from build to build.
 
 All the APIs you export ([`analyze`](#analyze), [`build`](#build) and [`prepareCache`](#preparecache)) are not guaranteed to be run in the same process, but the filesystem we expose (e.g.: `workPath` and the results of calling [`getWriteableDirectory`](#getWriteableDirectory) ) is retained.
 
@@ -165,8 +165,6 @@ When a new build is created, we pre-populate the `workPath` supplied to `analyze
 
 The `analyze` step can modify that directory, and it will not be re-created when it's supplied to `build` and `prepareCache`.
 
-To learn how the cache key is computed and invalidated, refer to the [overview](https://zeit.co/docs/v2/advanced/runtimes#technical-details).
-
 ### Accessing Environment and Secrets
 
 The env and secrets specified by the user as `build.env` are passed to the Runtime process. This means you can access user env via `process.env` in Node.js.

README.md

@@ -1,15 +1,19 @@
-![now](https://assets.zeit.co/image/upload/v1581518533/repositories/now-cli/v4.png)
+<p align="center">
+  <img src="https://assets.vercel.com/image/upload/v1588805858/repositories/vercel/logo.png" height="96">
+  <h3 align="center">Vercel</h3>
+  <p align="center">Develop. Preview. Ship.</p>
+</p>
 
 [![CI Status](https://badgen.net/github/checks/zeit/now?label=CI)](https://github.com/zeit/now/actions?workflow=CI)
 [![Join the community on GitHub Discussions](https://badgen.net/badge/join%20the%20discussion/on%20github/black?icon=github)](https://github.com/zeit/now/discussions)
 
 ## Usage
 
-Get started by [Importing a Git Project](https://zeit.co/import) and use `git push` to deploy. Alternatively, you can [install Now CLI](https://zeit.co/download).
+Get started by [Importing a Git Project](https://vercel.com/import) and use `git push` to deploy. Alternatively, you can [install Vercel CLI](https://vercel.com/download).
 
 ## Documentation
 
-For details on how to use ZEIT Now, check out our [documentation](https://zeit.co/docs).
+For details on how to use Vercel, check out our [documentation](https://vercel.com/docs).
 
 ## Caught a Bug?
 
@@ -17,7 +21,7 @@ For details on how to use ZEIT Now, check out our [documentation](https://zeit.c
 2. Install dependencies with `yarn install`
 3. Compile the code: `yarn build`
 4. Link the package to the global module directory: `cd ./packages/now-cli && yarn link`
-5. You can now start using `now` anywhere inside the command line
+5. You can start using `vercel` anywhere inside the command line
 
 As always, you should use `yarn test-unit` to run the tests and see if your changes have broken anything.
 

api/_lib/util/with-api-handler.ts

@@ -17,9 +17,9 @@ export function withApiHandler(handler: Handler): Handler {
     }
 
     if (req.method !== 'GET') {
-      return res.status(404).json({
+      return res.status(405).json({
         error: {
-          code: 'not_found',
+          code: 'method_not_allowed',
           message: 'Only GET requests are supported for this endpoint.',
         },
       });

api/frameworks.ts

@@ -19,5 +19,8 @@ export default withApiHandler(async function(
   req: NowRequest,
   res: NowResponse
 ) {
+  res.setHeader('Access-Control-Allow-Origin', '*');
+  res.setHeader('Access-Control-Allow-Methods', 'GET');
+  res.setHeader('Access-Control-Allow-Headers', 'Authorization, Accept, Content-Type');
   return res.status(200).json(frameworks);
 });

errors/cant-solve-challenge.md

@@ -8,7 +8,7 @@ the provider couldn’t solve the requested challenges.
 
 ## How to Fix It
 
-If your domain is pointing to ZEIT World DNS and you’re getting this error,
+If your domain is pointing to Vercel DNS and you’re getting this error,
 it could be that:
 
 - The domain was acquired recently, and it might not be ready for use yet.
@@ -17,11 +17,11 @@ it could be that:
 When running into this, ensure that your nameservers are configured correctly. Also, if you bought the domain recently or have made changes, please be patient,
 it might take a while for these to be ready.
 
-If your domain is _not_ pointing to ZEIT World DNS and you’re getting this
+If your domain is _not_ pointing to Vercel DNS and you’re getting this
 error, the following methods could help:
 
-- When solving challenges *manually*, ensure that the TXT
-records required to solve the challenges exist and are propagated. You can do so by querying the nameservers with `nslookup -q=TXT _acme-challenge.domain.com` depending on the Common Names you want for your certificate.
+- When solving challenges _manually_, ensure that the TXT
+  records required to solve the challenges exist and are propagated. You can do so by querying the nameservers with `nslookup -q=TXT _acme-challenge.domain.com` depending on the Common Names you want for your certificate.
 
 - If you are not solving the challenges manually you must ensure that you have an
-`ALIAS` and `CNAME` records in place. Ensure also that you have disabled automatic redirects to `https` and ensure all changes were propagated.
+  `ALIAS` and `CNAME` records in place. Ensure also that you have disabled automatic redirects to `https` and ensure all changes were propagated.

errors/deploy-invalid-dc.md

@@ -7,9 +7,9 @@ used an unknown or invalid dc identifier.
 
 #### Possible Ways to Fix It
 
-Check your `now.json` or `--regions` flag and
+Check your `vercel.json` or `--regions` flag and
 make sure you are using a valid string. Regions
-and DCs have to be in *lowercase*.
+and DCs have to be in _lowercase_.
 
 **Valid region identifiers**:
 
@@ -19,7 +19,7 @@ and DCs have to be in *lowercase*.
 - `gru`
 - `iad`
 
-In `now-cli`, they currently are transformed to 
+In `now-cli`, they currently are transformed to
 DC identifiers before being sent to our APIs.
 
 **Valid DC identifiers**:

errors/dns-configuration-error.md

@@ -4,12 +4,12 @@
 
 When generating a certificate, we have to prove ownership over the domain
 for the Certificate Authority (CA) that issues it. We also run some pretests
-to make sure the DNS is properly configured before submitting the request to 
+to make sure the DNS is properly configured before submitting the request to
 the CA. This error means that these pretests did not succeed.
 
 ## How to Fix It
 
-If your domain is pointing to ZEIT World DNS and you’re getting this error,
+If your domain is pointing to Vercel DNS and you’re getting this error,
 it could be that:
 
 - The domain was acquired recently, and it might not be ready for use yet.
@@ -18,6 +18,6 @@ it could be that:
 When running into this, ensure that your nameservers have configuration is correct. Also, if you bought the domain recently or have made changes, please be patient,
 it might take a while for these to be ready.
 
-If your domain is _not_ pointing to ZEIT World DNS and you’re getting this
+If your domain is _not_ pointing to Vercel DNS and you’re getting this
 error, you must ensure that you have an `ALIAS` and `CNAME` records in place.
 Ensure also that you have disabled automatic redirects to `https` and ensure all changes were propagated.

errors/domain-verification.md

@@ -12,10 +12,10 @@ You can retrieve both the intended nameservers and TXT verification record for t
 
 When you have added either verification method to your domain, you can run `now domains verify <domain>` again to complete verification for your domain.
 
-ZEIT will also automatically check periodically that your domain has been verified and automatically mark it as such if we detect either verification method on the domain.
+Vercel will also automatically check periodically that your domain has been verified and automatically mark it as such if we detect either verification method on the domain.
 
 If you would not like to verify your domain, you can remove it from your account using `now domains rm <domain>`.
 
 #### Resources
-- [ZEIT Domains Documentation](https://zeit.co/docs/v2/domains-and-aliases/adding-a-domain/)
-- [Zero-Downtime Domain Migration Guide](https://zeit.co/docs/v2/domains-and-aliases/zero-downtime-domain-migration/)
+
+- [Vercel Custom Domains Documentation](https://vercel.com/docs/v2/custom-domains)

errors/invalid-route-source.md

@@ -13,7 +13,7 @@ Wrap the `RegExp` part of your `source` as an un-named parameter.
 ```js
 {
   source: '/feedback/(?!general)',
-  destination: '/feedback/general'
+  destination: '/api/feedback/general'
 }
 ```
 
@@ -22,7 +22,27 @@ Wrap the `RegExp` part of your `source` as an un-named parameter.
 ```js
 {
   source: '/feedback/((?!general).*)',
-  destination: '/feedback/general'
+  destination: '/api/feedback/general'
+}
+```
+
+Ensure any segments used in the `destination` property are also used in the `source` property.
+
+**Before**
+
+```js
+{
+  source: '/feedback/:type',
+  destination: '/api/feedback/:id'
+}
+```
+
+**After**
+
+```js
+{
+  source: '/feedback/:id',
+  destination: '/api/feedback/:id'
 }
 ```
 

errors/invalid-token-value.md

@@ -8,4 +8,4 @@ The `--token` flag was specified, but its contents are invalid.
 
 The `--token` flag must only contain numbers (0-9) and letters from the alphabet (a-z and A-Z). This needs to be the token of the user account as which you'd like to act.
 
-You can either get the token from the `./now/auth.json` file located in your user directory or [from the dashboard](https://zeit.co/account/tokens).
+You can either get the token from the `./vercel/auth.json` file located in your user directory or [from the dashboard](https://vercel.com/account/tokens).

errors/missing-env-file.md

@@ -1,7 +1,8 @@
 # Missing Environment Variables While Developing
 
 #### Why This Error Occurred
-You ran `now dev` inside a project that contains a `now.json` file with `env` or `build.env` properties that use [Now Secrets](https://zeit.co/docs/v2/deployments/environment-variables-and-secrets).
+
+You ran `now dev` inside a project that contains a `vercel.json` file with `env` or `build.env` properties that use [Now Secrets](https://vercel.com/docs/v2/build-step#environment-variables).
 
 In order to use environment variables in your project locally that have values defined using the Now Secrets format (e.g. `@my-secret-value`), you will need to provide the value as an environment variable using a `.env` or `.env.build` file.
 
@@ -23,4 +24,4 @@ TEST=value
 
 In the above example, `TEST` represents the name of the environment variable and `value` its value.
 
-For more information on Environment Variables in development, [see the documentation](https://zeit.co/docs/v2/development/environment-variables/).
+For more information on Environment Variables in development, [see the documentation](https://vercel.com/docs/v2/build-step#environment-variables).

errors/missing-scope-value.md

@@ -8,4 +8,4 @@ The `--scope` flag was specified, but there's no value for it available.
 
 In order to make it work, you need to specify a value for the `--scope` flag. This needs to be the slug or ID of the team as which you'd like to act or the username or ID of a user you'd like to act as.
 
-As an example, if your team URL is `https://zeit.co/teams/zeit`, you would set `--scope` to `zeit`.
+As an example, if your team URL is `https://vercel.com/teams/zeit`, you would set `--scope` to `zeit`.

errors/missing-token-value.md

@@ -8,4 +8,4 @@ The `--token` flag was specified, but there's no value for it available.
 
 In order to make it work, you need to specify a value for the `--token` flag. This needs to be the token of the user account as which you'd like to act.
 
-You can either get the token from the `./now/auth.json` file located in your user directory or [from the dashboard](https://zeit.co/account/tokens).
+You can either get the token from the `./vercel/auth.json` file located in your user directory or [from the dashboard](https://vercel.com/account/tokens).

errors/no-credentials-found.md

@@ -6,5 +6,5 @@ You're running Now CLI in a non-terminal context and there are no credentials av
 
 #### Possible Ways to Fix It
 
-- Specify a value for the `--token` flag (this needs to be the token of the user account as which you'd like to act). You can either get the token from the `./now/auth.json` file located in your user directory or [from the dashboard](https://zeit.co/account/tokens).
-- Ensure that both `~/now/auth.json` and `~/now/config.json` exist
+- Specify a value for the `--token` flag (this needs to be the token of the user account as which you'd like to act). You can either get the token from the `./vercel/auth.json` file located in your user directory or [from the dashboard](https://vercel.com/account/tokens).
+- Ensure that both `~/vercel/auth.json` and `~/vercel/config.json` exist

errors/no-token-allowed.md

@@ -8,4 +8,4 @@ In turn, they would have to take the value of the `--token` flag into considerat
 
 #### Possible Ways to Fix It
 
-Specify a value for the `--scope` flag. This needs to be the slug or ID of the team as which you'd like to act (as an example, if your team URL is `https://zeit.co/teams/zeit`, the value can be `zeit`) or the username or ID of a user you'd like to act as.
+Specify a value for the `--scope` flag. This needs to be the slug or ID of the team as which you'd like to act (as an example, if your team URL is `https://vercel.com/teams/zeit`, the value can be `zeit`) or the username or ID of a user you'd like to act as.

errors/now-next-legacy-mode.md

@@ -27,7 +27,7 @@ Serverless:
 - Runs `npm run now-build`
 - Does not run `npm install --production` as the output from the build is all that's needed to bundle lambdas.
 - No runtime dependencies, meaning smaller lambda functions
-- Optimized for fast [cold start](https://zeit.co/blog/serverless-ssr#cold-start)
+- Optimized for fast [cold start](https://vercel.com/blog/serverless-ssr#cold-start)
 
 #### Possible Ways to Fix It
 

errors/now-next-routes-manifest.md

@@ -0,0 +1,11 @@
+# Routes Manifest Could Not Be Found
+
+#### Why This Error Occurred
+
+This could be caused by a failure during the build or an incorrect output directory being configured for your Next.js project.
+
+#### Possible Ways to Fix It
+
+Check for any build errors in the logs and ensure that the output directory setting is either not changed or is pointing to the location of the `.next` output folder (`distDir`).
+
+If you are running `next export` you should **not** need to customize the output directory to `out` since the builder automatically detects `next export` being run and uses the output from it.

errors/now-static-build-failed-to-detect-a-server.md

@@ -19,7 +19,7 @@ the provided `$PORT` that the builder expects the server to bind to.
 For example, if you are using Gatsby, your `now-dev` script must use the `-p`
 (port) option to bind to the `$PORT` specified from the builder:
 
-> *In Windows environments, reference the `PORT` environment variable with `%PORT%`*
+> _In Windows environments, reference the `PORT` environment variable with `%PORT%`_
 
 ```
 {
@@ -34,7 +34,3 @@ For example, if you are using Gatsby, your `now-dev` script must use the `-p`
 Consult your static builder program's `--help` or documentation to figure out what
 the command line flag to bind to a specific port is (in many cases, it is one of:
 `-p` / `-P` / `--port`).
-
-### Useful Links
-
-- [`@now/static-build` Local Development Documentation](https://zeit.co/docs/v2/deployments/official-builders/static-build-now-static-build#local-development)

errors/scaling-path-alias.md

@@ -9,4 +9,4 @@ You tried to use `now scale` on a path alias (`now alias -r rules.json`).
 Path aliases are routes to instances. Instances can be scaled independent from each other.
 You can view path aliases by running `now alias ls <id>`.
 
-Documentation for Path Aliases can be found [here](https://zeit.co/docs/features/path-aliases).
+Documentation for Path Aliases can be found [here](https://vercel.com/docs/features/path-aliases).

errors/solve-challenges-manually.md

@@ -3,18 +3,18 @@
 ## Why This Error Occurred
 
 When generating a certificate, we have to prove ownership over the domain
-for the Certificate Authority (CA) that issues it. In the case of Wildcard Certificates, 
-the requested challenge consists of adding TXT DNS records so, when the domain does not 
-point to ZEIT World DNS, we cannot create the records to solve the challenge.
+for the Certificate Authority (CA) that issues it. In the case of Wildcard Certificates,
+the requested challenge consists of adding TXT DNS records so, when the domain does not
+point to Vercel DNS, we cannot create the records to solve the challenge.
 
 ## How to Fix It
 
 To generate a certificate solving challenges manually, you must add the given `TXT` records with
-the appropriate name to your DNS. Then, after verifying that the CA can read the records, 
+the appropriate name to your DNS. Then, after verifying that the CA can read the records,
 you can rerun the issuance command.
 
-In case you want to start issuing a certificate to get the records you have to add or to 
+In case you want to start issuing a certificate to get the records you have to add or to
 get those records again in the console, You can run the issuance command including the
 `--challenge-only` option. This way the CLI will output the challenges information and,
-after adding those records, you can rerun the command without `--challenge-only` to finish 
+after adding those records, you can rerun the command without `--challenge-only` to finish
 issuance.

errors/v2-no-min.md

@@ -7,11 +7,10 @@ setting. This isn't supported yet.
 
 #### Possible Ways to Fix It
 
-Ensure your scale settings (in `now.json`, the command you're running 
+Ensure your scale settings (in `vercel.json`, the command you're running
 or from a previous deployment who's alias you're trying to overwrite) has
-the `min` scale setting set to `0`. You can do this by running 
+the `min` scale setting set to `0`. You can do this by running
 
 ```
 now scale <deployment> 0 10
 ```
-

errors/verification-timeout.md

@@ -13,7 +13,7 @@ but it couldn't do so within the allotted time (defaults to 2 minutes).
 Instance verification is the process of ensuring that after
 your deployment is ready, we can actually run (instantiate) your code.
 
-If you configured [regions or scale](https://zeit.co/docs/features/scaling),
+If you configured [regions or scale](https://vercel.com/docs/features/scaling),
 we ensure the minimums and maximums are met for the regions you enabled.
 
 If you think your code is taking too long to instantiate, this can be due

examples/README.md

@@ -1,18 +1,18 @@
-# ZEIT Now Examples
+# Vercel Examples
 
-This is the public list of examples for **ZEIT Now**.
+This is the public list of examples for **Vercel**.
 
 All of these ready to deploy examples feature a frontend framework or static site, created with zero configuration using the CLI tools they provide.
 
 The `+functions` examples feature an `/api` directory as well, highlighting how to use serverless functions on top of a framework, again with zero configuration required.
 
-## What is ZEIT Now?
+## What is Vercel?
 
-ZEIT Now is a cloud platform for static frontends and serverless functions. It enables developers to host websites and web applications that deploy instantly, scale automatically, and require no supervision.
+Vercel is a cloud platform for static frontends and serverless functions. It enables developers to host websites and web applications that deploy instantly, scale automatically, and require no supervision.
 
 ## What Does this Repository Contain?
 
-This repository consists of multiple examples, created for use with the [ZEIT Now](https://zeit.co/now) platform. In addition to this, it also contains:
+This repository consists of multiple examples, created for use with the [Vercel](https://vercel.com) platform. In addition to this, it also contains:
 
 - [Code of Conduct](https://github.com/zeit/now/blob/master/.github/CODE_OF_CONDUCT.md) - our Code of Conduct, adapted from the [Contributor Covenant](http://contributor-covenant.org)
 - [Contributing Guidelines](https://github.com/zeit/now/blob/master/.github/CONTRIBUTING.md) - a guide on how to contribute to the Now Examples repository
@@ -22,7 +22,7 @@ We recommend familiarizing yourself with the above sections, particularly if you
 
 ## Deploying Examples
 
-To get started using any of these examples as your own project, [install Now](https://zeit.co/download) and use either of the following commands in your terminal:
+To get started using any of these examples as your own project, [install Now](https://vercel.com/download) and use either of the following commands in your terminal:
 
 ```sh
 now init                    # Pick an example in the CLI
@@ -54,9 +54,9 @@ For example, the previous `nodejs` example showed a static frontend with a Node.
 
 ## Migrating and Upgrading
 
-If you have an existing project you would like to deploy with ZEIT Now, we recommend reading our guide on [migrating to Now and zero configuration](https://zeit.co/guides/migrate-to-zeit-now/). By combining the guide with this repository, you will quickly be able to understand how to deploy your application.
+If you have an existing project you would like to deploy with Vercel, we recommend reading our guide on [migrating to Vercel and zero configuration](https://vercel.com/guides/migrate-to-vercel). By combining the guide with this repository, you will quickly be able to understand how to deploy your application.
 
-If you would like to upgrade a project to take advantage of zero configuration, you may find the [upgrade guide](https://zeit.co/guides/upgrade-to-zero-configuration/) useful. The upgrade guide covers how to remove configuration from existing projects along with how to use the `/api` directory.
+If you would like to upgrade a project to take advantage of zero configuration, you may find the [upgrade guide](https://vercel.com/guides/upgrade-to-zero-configuration) useful. The upgrade guide covers how to remove configuration from existing projects along with how to use the `/api` directory.
 
 ## How to Contribute
 
@@ -80,6 +80,6 @@ Now Examples is an open source project released under the [MIT License](https://
 
 ## Get In Touch
 
-If you have any questions that are not covered by raising an issue then please get in touch with us on [GitHub Discussions](https://github.com/zeit/now/discussions). There you will find both members of the community and staff who are happy to help answer questions on anything ZEIT related.
+If you have any questions that are not covered by raising an issue then please get in touch with us on [GitHub Discussions](https://github.com/zeit/now/discussions). There you will find both members of the community and staff who are happy to help answer questions on anything Vercel related.
 
 [![Join the community on GitHub Discussions](https://badgen.net/badge/join%20the%20discussion/on%20github/black?icon=github)](https://github.com/zeit/now/discussions)

examples/amp/README.md

@@ -1,18 +1,18 @@
 # AMP Example
 
-This directory is a brief example of an [AMP](https://amp.dev/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of an [AMP](https://amp.dev/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own AMP project with ZEIT Now.
+Deploy your own AMP project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/amp)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/amp)
 
 _Live Example: https://amp.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started deploying AMP with ZEIT Now, you can use the [Now CLI](https://zeit.co/download) to initialize the project:
+To get started deploying AMP with Vercel, you can use the [Now CLI](https://vercel.com/download) to initialize the project:
 
 ```shell
 $ now init amp

examples/angular/README.md

@@ -2,13 +2,13 @@
 
 # Angular Example
 
-This directory is a brief example of an [Angular](https://angular.io/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of an [Angular](https://angular.io/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Angular project with ZEIT Now.
+Deploy your own Angular project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/angular)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/angular)
 
 _Live Example: https://angular.now-examples.now.sh_
 
@@ -22,7 +22,7 @@ $ ng new
 
 ### Deploying From Your Terminal
 
-You can deploy your new Angular project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Angular project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/brunch/README.md

@@ -1,18 +1,18 @@
 # Brunch Example
 
-This directory is a brief example of a [Brunch](https://brunch.io/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Brunch](https://brunch.io/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Brunch project with ZEIT Now.
+Deploy your own Brunch project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/brunch)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/brunch)
 
 _Live Example: https://brunch.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started deploying Brunch with ZEIT Now, you can use the [Brunch CLI](https://brunch.io/docs/commands) to initialize the project:
+To get started deploying Brunch with Vercel, you can use the [Brunch CLI](https://brunch.io/docs/commands) to initialize the project:
 
 ```shell
 $ brunch new project-name -s es6
@@ -20,7 +20,7 @@ $ brunch new project-name -s es6
 
 ### Deploying From Your Terminal
 
-You can deploy your new Brunch project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Brunch project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/brunch/app/assets/index.html

@@ -12,6 +12,6 @@
   <div class="brunch">
     <img src="/brunch-napkin.svg" alt="Brunch">
     <h4>Bon Appétit.</h4>
-    <h6>A <a href="http://brunch.io" target="_blank">Brunch</a> website deployed on <a href="https://zeit.co" target="_blank">ZEIT Now</a></h6>
+    <h6>A <a href="http://brunch.io" target="_blank">Brunch</a> website deployed on <a href="https://vercel.com" target="_blank">Vercel</a></h6>
   </div>
 </body>

examples/create-react-app/README.md

@@ -2,19 +2,19 @@
 
 # React Example
 
-This directory is a brief example of a [React](https://reactjs.org/) app with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction) that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [React](https://reactjs.org/) app with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction) that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own React project, along with Serverless Functions, with ZEIT Now.
+Deploy your own React project, along with Serverless Functions, with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/create-react-app-functions)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/create-react-app-functions)
 
 _Live Example: https://create-react-app.now-examples.now.sh/_
 
 ### How We Created This Example
 
-To get started with React, along with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction), with ZEIT Now, you can use the [Create-React-App CLI](https://reactjs.org/docs/create-a-new-react-app.html#create-react-app) to initialize the project:
+To get started with React, along with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction), with Vercel, you can use the [Create-React-App CLI](https://reactjs.org/docs/create-a-new-react-app.html#create-react-app) to initialize the project:
 
 ```shell
 $ npx create-react-app my-app
@@ -22,7 +22,7 @@ $ npx create-react-app my-app
 
 ### Deploying From Your Terminal
 
-You can deploy your new React project, along with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new React project, along with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/create-react-app/src/App.js

@@ -18,11 +18,11 @@ function App() {
       <h2>
         Deployed with{' '}
         <a
-          href="https://zeit.co/docs"
+          href="https://vercel.com/docs"
           target="_blank"
           rel="noreferrer noopener"
         >
-          ZEIT Now
+          Vercel
         </a>
         !
       </h2>

examples/custom-build/README.md

@@ -1,18 +1,18 @@
 # Custom Build Example
 
-This directory is a brief example of using a Custom Build script that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of using a Custom Build script that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Custom Built project with ZEIT Now.
+Deploy your own Custom Built project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/custom-build)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/custom-build)
 
 _Live Example: https://custom-build.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started deploying a Custom Built project with ZEIT Now, you can use the [Now CLI](https://zeit.co/download) to initialize the project:
+To get started deploying a Custom Built project with Vercel, you can use the [Now CLI](https://vercel.com/download) to initialize the project:
 
 ```shell
 $ now init custom-build
@@ -20,7 +20,7 @@ $ now init custom-build
 
 ### Deploying From Your Terminal
 
-You can deploy your new Custom Built project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Custom Built project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/docusaurus/README.md

@@ -2,19 +2,19 @@
 
 # Docusaurus Example
 
-This directory is a brief example of a [Docusaurus](https://docusaurus.io/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Docusaurus](https://docusaurus.io/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Docusaurus project with ZEIT Now.
+Deploy your own Docusaurus project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/docusaurus)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/docusaurus)
 
 _Live Example: https://docusaurus.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Docusaurus for deployment with ZEIT Now, you can use the [Docusaurus CLI](https://docusaurus.io/docs/en/installation) to initialize the project:
+To get started with Docusaurus for deployment with Vercel, you can use the [Docusaurus CLI](https://docusaurus.io/docs/en/installation) to initialize the project:
 
 ```shell
 $ docusaurus-init
@@ -22,7 +22,7 @@ $ docusaurus-init
 
 ### Deploying From Your Terminal
 
-You can deploy your new Docusaurus project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Docusaurus project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/dojo/README.md

@@ -1,16 +1,16 @@
 # Dojo Example
 
-This directory is a brief example of a [Dojo](https://dojo.io) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Dojo](https://dojo.io) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Dojo project with ZEIT Now.
+Deploy your own Dojo project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now-examples/tree/master/dojo)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now-examples/tree/master/dojo)
 
 ### How We Created This Example
 
-To get started with Dojo on Now, you can use the [Dojo CLI](https://github.com/dojo/cli) to initialize the project:
+To get started with Dojo on Vercel, you can use the [Dojo CLI](https://github.com/dojo/cli) to initialize the project:
 
 ```shell
 $ now init dojo

examples/eleventy/README.md

@@ -2,19 +2,19 @@
 
 # Eleventy Example
 
-This directory is a brief example of a [Eleventy](https://www.11ty.io/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Eleventy](https://www.11ty.io/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Eleventy project with ZEIT Now.
+Deploy your own Eleventy project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/eleventy)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/eleventy)
 
 _Live Example: https://eleventy.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Eleventy for deployment with ZEIT Now, you can use [npx](https://www.npmjs.com/package/npx) to initialize the project:
+To get started with Eleventy for deployment with Vercel, you can use [npx](https://www.npmjs.com/package/npx) to initialize the project:
 
 ```shell
 $ npx degit 11ty/eleventy-base-blog my-11ty-project
@@ -22,7 +22,7 @@ $ npx degit 11ty/eleventy-base-blog my-11ty-project
 
 ### Deploying From Your Terminal
 
-You can deploy your new Eleventy project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Eleventy project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/ember/README.md

@@ -2,19 +2,19 @@
 
 # Ember Example
 
-This directory is a brief example of an [Ember](https://emberjs.com/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of an [Ember](https://emberjs.com/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Ember project with ZEIT Now.
+Deploy your own Ember project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/ember)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/ember)
 
 _Live Example: https://ember.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Ember for deployment with ZEIT Now, you can use the [Ember CLI](https://ember-cli.com/) to initialize the project:
+To get started with Ember for deployment with Vercel, you can use the [Ember CLI](https://ember-cli.com/) to initialize the project:
 
 ```shell
 $ npx ember-cli new ember-project
@@ -22,7 +22,7 @@ $ npx ember-cli new ember-project
 
 ### Deploying From Your Terminal
 
-You can deploy your new Ember project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Ember project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/gatsby/README.md

@@ -2,19 +2,19 @@
 
 # Gatsby Example
 
-This directory is a brief example of a [Gatsby](https://www.gatsbyjs.org/) app with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction) that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Gatsby](https://www.gatsbyjs.org/) app with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction) that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Gatsby project, along with Serverless Functions, with ZEIT Now.
+Deploy your own Gatsby project, along with Serverless Functions, with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/gatsby)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/gatsby)
 
 _Live Example: https://gatsby.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Gatsby on Now, you can use the [Gatsby CLI](https://www.gatsbyjs.org/docs/gatsby-cli/) to initialize the project:
+To get started with Gatsby on Vercel, you can use the [Gatsby CLI](https://www.gatsbyjs.org/docs/gatsby-cli/) to initialize the project:
 
 ```shell
 $ gatsby new gatsby-site
@@ -22,7 +22,7 @@ $ gatsby new gatsby-site
 
 ### Deploying From Your Terminal
 
-You can deploy your new Gatsby project, along with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Gatsby project, along with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/gatsby/gatsby-config.js

@@ -8,7 +8,7 @@ module.exports = {
       resolve: `gatsby-plugin-manifest`,
       options: {
         name: 'Gatsby + Node.js (TypeScript) API',
-        short_name: 'Gatbsy + Node.js (TypeScript)',
+        short_name: 'Gatsby + Node.js (TypeScript)',
         start_url: '/',
         icon: 'src/images/gatsby-icon.png',
       },

examples/gatsby/src/pages/index.js

@@ -21,11 +21,11 @@ function Index() {
       <h2>
         Deployed with{' '}
         <a
-          href="https://zeit.co/docs"
+          href="https://vercel.com/docs"
           target="_blank"
           rel="noreferrer noopener"
         >
-          ZEIT Now
+          Vercel
         </a>
         !
       </h2>

examples/gridsome/README.md

@@ -2,19 +2,19 @@
 
 # Gridsome Example
 
-This directory is a brief example of a [Gridsome](https://gridsome.org/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Gridsome](https://gridsome.org/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Gridsome project with ZEIT Now.
+Deploy your own Gridsome project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/gridsome)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/gridsome)
 
 _Live Example: https://gridsome.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Gridsome for deployment with ZEIT Now, you can use the [Gridsome CLI](https://gridsome.org/docs/gridsome-cli/) to initialize the project:
+To get started with Gridsome for deployment with Vercel, you can use the [Gridsome CLI](https://gridsome.org/docs/gridsome-cli/) to initialize the project:
 
 ```shell
 $ gridsome create my-website
@@ -22,7 +22,7 @@ $ gridsome create my-website
 
 ### Deploying From Your Terminal
 
-You can deploy your new Gridsome project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Gridsome project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/hexo/README.md

@@ -2,19 +2,19 @@
 
 # Hexo Example
 
-This directory is a brief example of a [Hexo](https://hexo.io/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Hexo](https://hexo.io/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Hexo project with ZEIT Now.
+Deploy your own Hexo project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/hexo)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/hexo)
 
 _Live Example: https://hexo.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Hexo for deployment with ZEIT Now, you can use the [Hexo CLI](https://hexo.io/docs/index.html#Installation) to initialize the project:
+To get started with Hexo for deployment with Vercel, you can use the [Hexo CLI](https://hexo.io/docs/index.html#Installation) to initialize the project:
 
 ```shell
 $ hexo init project-name
@@ -22,7 +22,7 @@ $ hexo init project-name
 
 ### Deploying From Your Terminal
 
-You can deploy your new Hexo project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Hexo project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/hugo/README.md

@@ -1,18 +1,18 @@
 # Hugo Example
 
-This directory is a brief example of a [Hugo](https://gohugo.io/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Hugo](https://gohugo.io/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Hugo project with ZEIT Now.
+Deploy your own Hugo project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/hugo)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/hugo)
 
 _Live Example: https://hugo.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Hugo for deployment with ZEIT Now, you can use the [Hugo CLI](https://gohugo.io/commands/) to initialize the project:
+To get started with Hugo for deployment with Vercel, you can use the [Hugo CLI](https://gohugo.io/commands/) to initialize the project:
 
 ```shell
 $ hugo new site project-name
@@ -20,7 +20,7 @@ $ hugo new site project-name
 
 ### Deploying From Your Terminal
 
-You can deploy your new Hugo project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Hugo project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/hugo/content/posts/my-first-post.md

@@ -4,4 +4,4 @@ date: 2019-07-18T17:18:05+01:00
 draft: false
 ---
 
-# Hugo on ZEIT Now
+# Hugo on Vercel

examples/ionic-react/public/assets/shapes.svg

@@ -0,0 +1 @@
+<svg width="350" height="140" xmlns="http://www.w3.org/2000/svg" style="background:#f6f7f9"><g fill="none" fill-rule="evenodd"><path fill="#F04141" style="mix-blend-mode:multiply" d="M61.905-34.23l96.194 54.51-66.982 54.512L22 34.887z"/><circle fill="#10DC60" style="mix-blend-mode:multiply" cx="155.5" cy="135.5" r="57.5"/><path fill="#3880FF" style="mix-blend-mode:multiply" d="M208.538 9.513l84.417 15.392L223.93 93.93z"/><path fill="#FFCE00" style="mix-blend-mode:multiply" d="M268.625 106.557l46.332-26.75 46.332 26.75v53.5l-46.332 26.75-46.332-26.75z"/><circle fill="#7044FF" style="mix-blend-mode:multiply" cx="299.5" cy="9.5" r="38.5"/><rect fill="#11D3EA" style="mix-blend-mode:multiply" transform="rotate(-60 148.47 37.886)" x="143.372" y="-7.056" width="10.196" height="89.884" rx="5.098"/><path d="M-25.389 74.253l84.86 8.107c5.498.525 9.53 5.407 9.004 10.905a10 10 0 0 1-.057.477l-12.36 85.671a10.002 10.002 0 0 1-11.634 8.42l-86.351-15.226c-5.44-.959-9.07-6.145-8.112-11.584l13.851-78.551a10 10 0 0 1 10.799-8.219z" fill="#7044FF" style="mix-blend-mode:multiply"/><circle fill="#0CD1E8" style="mix-blend-mode:multiply" cx="273.5" cy="106.5" r="20.5"/></g></svg>

examples/ionic-react/public/index.html

@@ -0,0 +1,30 @@
+<!DOCTYPE html>
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <title>Ionic App</title>
+
+    <base href="/" />
+
+    <meta
+      name="viewport"
+      content="viewport-fit=cover, width=device-width, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no"
+    />
+    <meta name="format-detection" content="telephone=no" />
+    <meta name="msapplication-tap-highlight" content="no" />
+
+    <link rel="manifest" href="%PUBLIC_URL%/manifest.json" />
+
+    <link rel="shortcut icon" type="image/png" href="%PUBLIC_URL%/assets/icon/favicon.png" />
+
+    <!-- add to homescreen for ios -->
+    <meta name="apple-mobile-web-app-capable" content="yes" />
+    <meta name="apple-mobile-web-app-title" content="Ionic App" />
+    <meta name="apple-mobile-web-app-status-bar-style" content="black" />
+  </head>
+
+  <body>
+    <div id="root"></div>
+  </body>
+
+</html>

examples/ionic-react/public/manifest.json

@@ -0,0 +1,21 @@
+{
+  "short_name": "Ionic App",
+  "name": "My Ionic App",
+  "icons": [
+    {
+      "src": "assets/icon/favicon.png",
+      "sizes": "64x64 32x32 24x24 16x16",
+      "type": "image/x-icon"
+    },
+    {
+      "src": "assets/icon/icon.png",
+      "type": "image/png",
+      "sizes": "512x512",
+      "purpose": "maskable"
+    }
+  ],
+  "start_url": ".",
+  "display": "standalone",
+  "theme_color": "#ffffff",
+  "background_color": "#ffffff"
+}

examples/ionic-react/readme.md

@@ -1,18 +1,18 @@
 # Ionic React Example
 
-This directory is a brief example of an [Ionic React](https://ionicframework.com/docs/react/overview) app that can be deployed with ZEIT Now and zero configuration
+This directory is a brief example of an [Ionic React](https://ionicframework.com/docs/react/overview) app that can be deployed with Vercel and zero configuration
 
 ## Deploy Your Own
 
-Deploy your own Ionic React project with ZEIT Now.
+Deploy your own Ionic React project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/ionic-react)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/ionic-react)
 
 _Live Example: https://ionic-react.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Ionic React deployed with ZEIT Now, you can use the [Ionic CLI](https://ionicframework.com/docs/cli) to initialize the project:
+To get started with Ionic React deployed with Vercel, you can use the [Ionic CLI](https://ionicframework.com/docs/cli) to initialize the project:
 
 ```shell
 $ npx ionic start [project-name] conference --type react && cd [project-name]
@@ -20,7 +20,7 @@ $ npx ionic start [project-name] conference --type react && cd [project-name]
 
 ### Deploying From Your Terminal
 
-You can deploy your new Ionic React project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Ionic React project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/jekyll/README.md

@@ -1,18 +1,18 @@
 # Jekyll Example
 
-This directory is a brief example of a [Jekyll](https://jekyllrb.com/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Jekyll](https://jekyllrb.com/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Jekyll project with ZEIT Now.
+Deploy your own Jekyll project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/jekyll)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/jekyll)
 
 _Live Example: https://jekyll.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Jekyll for deployment with ZEIT Now, you can use the [Jekyll CLI](https://jekyllrb.com/docs/usage/) to initialize the project:
+To get started with Jekyll for deployment with Vercel, you can use the [Jekyll CLI](https://jekyllrb.com/docs/usage/) to initialize the project:
 
 ```shell
 $ jekyll new my-blog
@@ -20,7 +20,7 @@ $ jekyll new my-blog
 
 ### Deploying From Your Terminal
 
-You can deploy your new Jekyll project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Jekyll project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/middleman/README.md

@@ -1,18 +1,18 @@
 # Middleman Example
 
-This directory is a brief example of a [Middleman](https://middlemanapp.com/) site that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Middleman](https://middlemanapp.com/) site that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Middleman project with ZEIT Now.
+Deploy your own Middleman project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/middleman)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/middleman)
 
 _Live Example: https://middleman.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Middleman for deployment with ZEIT Now, you can use the [Middleman CLI](https://middlemanapp.com/basics/start-new-site/) to initialize the project:
+To get started with Middleman for deployment with Vercel, you can use the [Middleman CLI](https://middlemanapp.com/basics/start-new-site/) to initialize the project:
 
 ```shell
 $ middleman init project-name
@@ -20,7 +20,7 @@ $ middleman init project-name
 
 ### Deploying From Your Terminal
 
-You can deploy your new Middleman project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Middleman project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/nextjs/README.md

@@ -21,10 +21,10 @@ To learn more about Next.js, take a look at the following resources:
 - [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
 - [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
 
-You can check out [the Next.js GitHub repository](https://github.com/zeit/next.js/) - your feedback and contributions are welcome!
+You can check out [the Next.js GitHub repository](https://github.com/zeit/next.js) - your feedback and contributions are welcome!
 
-## Deploy on ZEIT Now
+## Deploy on Vercel
 
-The easiest way to deploy your Next.js app is to use the [ZEIT Now Platform](https://zeit.co/import?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
+The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/import?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
 
 Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.

examples/nextjs/pages/index.js

@@ -36,12 +36,12 @@ const Home = () => (
         </a>
 
         <a
-          href="https://zeit.co/new?filter=next.js&utm_source=create-next-app&utm_medium=default-template&utm_campaign=create-next-app"
+          href="https://vercel.com/new?filter=next.js&utm_source=create-next-app&utm_medium=default-template&utm_campaign=create-next-app"
           className="card"
         >
           <h3>Deploy &rarr;</h3>
           <p>
-            Instantly deploy your Next.js site to a public URL with ZEIT Now.
+            Instantly deploy your Next.js site to a public URL with Vercel.
           </p>
         </a>
       </div>
@@ -49,11 +49,11 @@ const Home = () => (
 
     <footer>
       <a
-        href="https://zeit.co?utm_source=create-next-app&utm_medium=default-template&utm_campaign=create-next-app"
+        href="https://vercel.com?utm_source=create-next-app&utm_medium=default-template&utm_campaign=create-next-app"
         target="_blank"
         rel="noopener noreferrer"
       >
-        Powered by <img src="/zeit.svg" alt="ZEIT Logo" />
+        Powered by <img src="/vercel.svg" alt="Vercel Logo" />
       </a>
     </footer>
 

examples/nextjs/public/vercel.svg

@@ -0,0 +1,3 @@
+<svg width="70" height="16" viewBox="0 0 70 16" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <path d="M9.255.05l9.108 15.753H.148L9.255.05zM39.434 8.418c0-2.535-1.87-4.307-4.554-4.307-2.683 0-4.554 1.772-4.554 4.307 0 2.487 2.019 4.308 4.8 4.308 1.526 0 2.905-.566 3.79-1.6l-1.673-.96c-.517.517-1.28.837-2.117.837-1.23 0-2.29-.665-2.658-1.674l-.074-.172h6.966a3.76 3.76 0 00.074-.739zm-7.065-.738l.05-.148c.32-1.058 1.255-1.698 2.436-1.698 1.207 0 2.117.64 2.437 1.698l.05.148h-4.973zM65.945 8.418c0-2.535-1.871-4.307-4.554-4.307-2.683 0-4.554 1.772-4.554 4.307 0 2.487 2.018 4.308 4.8 4.308 1.526 0 2.904-.566 3.79-1.6l-1.673-.96c-.517.517-1.28.837-2.117.837-1.23 0-2.29-.665-2.659-1.674l-.073-.172h6.966a3.76 3.76 0 00.074-.739zM58.88 7.68l.05-.148c.32-1.058 1.255-1.698 2.436-1.698 1.206 0 2.117.64 2.437 1.698l.05.148H58.88zM54.13 7.015l1.673-.96c-.788-1.23-2.19-1.92-3.89-1.92-2.682 0-4.553 1.773-4.553 4.308 0 2.536 1.87 4.308 4.554 4.308 1.698 0 3.101-.69 3.89-1.92l-1.675-.96c-.443.738-1.23 1.157-2.215 1.157-1.55 0-2.585-1.034-2.585-2.585 0-1.55 1.034-2.585 2.585-2.585.96 0 1.772.419 2.215 1.157zM69.637 1.428h-1.97v11.077h1.97V1.428zM31.779 1.428h-2.265L25.182 8.91l-4.333-7.483H18.56l6.622 11.421 6.597-11.421zM45.71 6.4c.222 0 .444.025.665.074V4.382c-1.673.049-3.249.984-3.249 2.141V4.382h-1.97v8.123h1.97v-3.52c0-1.527 1.059-2.585 2.585-2.585z" fill="#000"/>
+</svg>

examples/nextjs/public/zeit.svg

@@ -1,10 +0,0 @@
-<svg width="82" height="16" fill="none" xmlns="http://www.w3.org/2000/svg">
-    <path fill="url(#prefix__paint0_linear)" d="M9.018 0l9.019 16H0L9.018 0z"/>
-    <path fill="#333" fill-rule="evenodd" d="M51.634 12.028h-6.492V2.052h6.492v1.256H46.61v3.007h4.37V7.57h-4.37v3.202h5.024v1.255zm-14.063 0h-7.235v-1.096l5.342-7.624h-5.253V2.052h7.058v1.097l-5.342 7.623h5.43v1.256zm21.88 0h6.333v-1.256h-2.423V3.308h2.423V2.052h-6.332v1.256h2.441v7.465h-2.441v1.255zm18.22 0h-1.468v-8.72h-3.36V2.052h8.225v1.256H77.67v8.72z" clip-rule="evenodd"/>
-    <defs>
-        <linearGradient id="prefix__paint0_linear" x1="28.022" x2="16.189" y1="22.991" y2="8.569" gradientUnits="userSpaceOnUse">
-            <stop stop-color="#fff"/>
-            <stop offset="1"/>
-        </linearGradient>
-    </defs>
-</svg>

examples/nuxtjs/README.md

@@ -1,18 +1,18 @@
 # Nuxt.js Example
 
-This directory is a brief example of a [Nuxt.js](https://nuxtjs.org) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Nuxt.js](https://nuxtjs.org) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Nuxt.js project with ZEIT Now.
+Deploy your own Nuxt.js project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/nuxtjs)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/nuxtjs)
 
 _Live Example: https://nuxtjs.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Nuxt.js deployed with ZEIT Now, you can use the [Create-Nuxt-App CLI](https://www.npmjs.com/package/create-nuxt-app) to initialize the project:
+To get started with Nuxt.js deployed with Vercel, you can use the [Create-Nuxt-App CLI](https://www.npmjs.com/package/create-nuxt-app) to initialize the project:
 
 ```shell
 $ npx create-nuxt-app my-app
@@ -22,7 +22,7 @@ $ npx create-nuxt-app my-app
 
 ### Deploying From Your Terminal
 
-You can deploy your new Nuxt.js project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Nuxt.js project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/polymer/README.md

@@ -2,19 +2,19 @@
 
 # Polymer Example
 
-This directory is a brief example of a [Polymer](https://www.polymer-project.org/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Polymer](https://www.polymer-project.org/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Polymer project with ZEIT Now.
+Deploy your own Polymer project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/polymer)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/polymer)
 
 _Live Example: https://polymer.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Polymer deployed with ZEIT Now, you can use the [Polymer CLI](https://polymer-library.polymer-project.org/3.0/docs/tools/polymer-cli) to initialize the project:
+To get started with Polymer deployed with Vercel, you can use the [Polymer CLI](https://polymer-library.polymer-project.org/3.0/docs/tools/polymer-cli) to initialize the project:
 
 ```shell
 $ polymer init
@@ -22,7 +22,7 @@ $ polymer init
 
 ### Deploying From Your Terminal
 
-You can deploy your new Polymer project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Polymer project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/preact/README.md

@@ -2,19 +2,19 @@
 
 # Preact Example
 
-This directory is a brief example of a [Preact](https://preactjs.com/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Preact](https://preactjs.com/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Preact project with ZEIT Now.
+Deploy your own Preact project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/preact)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/preact)
 
 _Live Example: https://preact.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Preact for deployment with ZEIT Now, you can use the [Preact CLI](https://github.com/preactjs/preact-cli) to initialize the project:
+To get started with Preact for deployment with Vercel, you can use the [Preact CLI](https://github.com/preactjs/preact-cli) to initialize the project:
 
 ```shell
 $ preact create default my-project
@@ -22,7 +22,7 @@ $ preact create default my-project
 
 ### Deploying From Your Terminal
 
-You can deploy your new Preact project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Preact project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/saber/README.md

@@ -2,19 +2,19 @@
 
 # Saber Example
 
-This directory is a brief example of a [Saber](https://saber.land) site that can be deployed to ZEIT Now with zero configuration.
+This directory is a brief example of a [Saber](https://saber.land) site that can be deployed to Vercel with zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Saber project with ZEIT Now.
+Deploy your own Saber project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/saber)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/saber)
 
 _Live Example: https://saber.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Saber on Now, you can use [`npm init`](https://docs.npmjs.com/cli/init) to initialize the project:
+To get started with Saber on Vercel, you can use [`npm init`](https://docs.npmjs.com/cli/init) to initialize the project:
 
 ```shell
 $ npm init site my-saber-site

examples/sapper/README.md

@@ -1,18 +1,18 @@
 # Sapper Example
 
-This directory is a brief example of a [Sapper](https://sapper.svelte.dev/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Sapper](https://sapper.svelte.dev/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Sapper project with ZEIT Now.
+Deploy your own Sapper project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/sapper)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/sapper)
 
 _Live Example: https://sapper.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Sapper deployed with ZEIT Now, you can use [degit](https://github.com/Rich-Harris/degit) to initialize the project:
+To get started with Sapper deployed with Vercel, you can use [degit](https://github.com/Rich-Harris/degit) to initialize the project:
 
 ```shell
 $ npx degit "sveltejs/sapper-template#webpack" my-sapper-app
@@ -22,7 +22,7 @@ $ npx degit "sveltejs/sapper-template#webpack" my-sapper-app
 
 ### Deploying From Your Terminal
 
-You can deploy your new Sapper project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Sapper project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/sapper/src/routes/blog/_posts.js

@@ -65,7 +65,7 @@ const posts = [
     title: 'How is Sapper different from Next.js?',
     slug: 'how-is-sapper-different-from-next',
     html: `
-			<p><a href='https://github.com/zeit/next.js'>Next.js</a> is a React framework from <a href='https://zeit.co'>Zeit</a>, and is the inspiration for Sapper. There are a few notable differences, however:</p>
+			<p><a href='https://github.com/zeit/next.js'>Next.js</a> is a React framework from <a href='https://vercel.com'>Zeit</a>, and is the inspiration for Sapper. There are a few notable differences, however:</p>
 
 			<ul>
 				<li>It's powered by <a href='https://svelte.dev'>Svelte</a> instead of React, so it's faster and your apps are smaller</li>

examples/scully/src/index.html

@@ -2,7 +2,7 @@
 <html lang="en">
 <head>
   <meta charset="utf-8">
-  <title>Scully on ZEIT Now</title>
+  <title>Scully on Vercel</title>
   <base href="/">
   <meta name="viewport" content="width=device-width, initial-scale=1">
   <link rel="icon" type="image/x-icon" href="favicon.ico">

examples/stencil/readme.md

@@ -1,18 +1,18 @@
 # Stencil Example
 
-This directory is a brief example of a [Stencil](https://stenciljs.com/) app that can be deployed with ZEIT Now and zero configuration
+This directory is a brief example of a [Stencil](https://stenciljs.com/) app that can be deployed with Vercel and zero configuration
 
 ## Deploy Your Own
 
-Deploy your own Stencil project with ZEIT Now.
+Deploy your own Stencil project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/stencil)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/stencil)
 
 _Live Example: https://stencil.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Stencil deployed with ZEIT Now, you can use the [Stencil project initializer](https://stenciljs.com/docs/getting-started#starting-a-new-project) to initialize the project:
+To get started with Stencil deployed with Vercel, you can use the [Stencil project initializer](https://stenciljs.com/docs/getting-started#starting-a-new-project) to initialize the project:
 
 ```shell
 $ npm init stencil
@@ -20,7 +20,7 @@ $ npm init stencil
 
 ### Deploying From Your Terminal
 
-You can deploy your new Stencil project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Stencil project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/svelte/README.md

@@ -1,18 +1,18 @@
 # Svelte Example
 
-This directory is a brief example of a [Svelte](https://svelte.dev/) app with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction) that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Svelte](https://svelte.dev/) app with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction) that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Svelte project, along with Serverless Functions, with ZEIT Now.
+Deploy your own Svelte project, along with Serverless Functions, with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/svelte)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/svelte)
 
 _Live Example: https://svelte.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Svelte, along with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction), deployed with ZEIT Now, you can use [degit](https://github.com/Rich-Harris/degit) to initialize the project:
+To get started with Svelte, along with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction), deployed with Vercel, you can use [degit](https://github.com/Rich-Harris/degit) to initialize the project:
 
 ```shell
 $ npx degit sveltejs/template my-svelte-project
@@ -20,7 +20,7 @@ $ npx degit sveltejs/template my-svelte-project
 
 ### Deploying From Your Terminal
 
-You can deploy your new Svelte project, along with [Serverless Functions](https://zeit.co/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Svelte project, along with [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction), with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/svelte/src/App.svelte

@@ -13,8 +13,8 @@
   <h1>Svelte + Node.js API</h1>
   <h2>
     Deployed with
-    <a href="https://zeit.co/docs" target="_blank" rel="noreferrer noopener">
-      ZEIT Now
+    <a href="https://vercel.com/docs" target="_blank" rel="noreferrer noopener">
+      Vercel
     </a>
     !
   </h2>

examples/umijs/README.md

@@ -2,19 +2,19 @@
 
 # UmiJS Example
 
-This directory is a brief example of a [UmiJS](https://umijs.org/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [UmiJS](https://umijs.org/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own UmiJS project with ZEIT Now.
+Deploy your own UmiJS project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/umijs)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/umijs)
 
 _Live Example: https://umijs.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with UmiJS deployed with ZEIT Now, you can use the [Umi CLI](https://github.com/umijs/create-umi) to initialize the project:
+To get started with UmiJS deployed with Vercel, you can use the [Umi CLI](https://github.com/umijs/create-umi) to initialize the project:
 
 ```shell
 $ yarn create umi app-name
@@ -22,7 +22,7 @@ $ yarn create umi app-name
 
 ### Deploying From Your Terminal
 
-You can deploy your new UmiJS project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new UmiJS project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

examples/vanilla-pusher-functions/README.md

@@ -4,7 +4,7 @@ This directory is a realtime serverless whiteboard powered by Pusher. The fronte
 
 ## Creating This Example
 
-To get started with a realtime whiteboard on Now, you can use [Now CLI](https://zeit.co/download) to initialize the project:
+To get started with a realtime whiteboard on Vercel, you can use [Now CLI](https://vercel.com/download) to initialize the project:
 
 ```shell
 $ now init vanilla-pusher-functions

examples/vue/README.md

@@ -2,19 +2,19 @@
 
 # Vue.js Example
 
-This directory is a brief example of a [Vue.js](https://vuejs.org/) app that can be deployed with ZEIT Now and zero configuration.
+This directory is a brief example of a [Vue.js](https://vuejs.org/) app that can be deployed with Vercel and zero configuration.
 
 ## Deploy Your Own
 
-Deploy your own Vue.js project with ZEIT Now.
+Deploy your own Vue.js project with Vercel.
 
-[![Deploy with ZEIT Now](https://zeit.co/button)](https://zeit.co/import/project?template=https://github.com/zeit/now/tree/master/examples/vue)
+[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/import/project?template=https://github.com/zeit/now/tree/master/examples/vue)
 
 _Live Example: https://vue.now-examples.now.sh_
 
 ### How We Created This Example
 
-To get started with Vue.js deployed with ZEIT Now, you can use the [Vue CLI](https://cli.vuejs.org/guide/creating-a-project.html#vue-create) to initialize the project:
+To get started with Vue.js deployed with Vercel, you can use the [Vue CLI](https://cli.vuejs.org/guide/creating-a-project.html#vue-create) to initialize the project:
 
 ```shell
 $ vue create
@@ -22,7 +22,7 @@ $ vue create
 
 ### Deploying From Your Terminal
 
-You can deploy your new Vue.js project with a single command from your terminal using [Now CLI](https://zeit.co/download):
+You can deploy your new Vue.js project with a single command from your terminal using [Now CLI](https://vercel.com/download):
 
 ```shell
 $ now

lerna.json

@@ -1,14 +1,13 @@
 {
-    "npmClient": "yarn",
-    "useWorkspaces": true,
-    "packages": ["packages/*"],
-    "command": {
-      "publish": {
-        "npmClient": "npm",
-        "allowBranch": ["master", "canary"],
-        "registry": "https://registry.npmjs.org/"
-      }
-    },
-    "version": "independent"
-  }
-  
+  "npmClient": "yarn",
+  "useWorkspaces": true,
+  "packages": ["packages/*"],
+  "command": {
+    "publish": {
+      "npmClient": "npm",
+      "allowBranch": ["master"],
+      "registry": "https://registry.npmjs.org/"
+    }
+  },
+  "version": "independent"
+}

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "now-builders",
+  "name": "vercel-monorepo",
   "version": "0.0.0",
   "private": true,
   "license": "MIT",
@@ -22,10 +22,12 @@
     "buffer-replace": "1.0.0",
     "eslint": "6.2.2",
     "eslint-config-prettier": "6.1.0",
+    "eslint-plugin-jest": "23.8.2",
     "husky": "3.0.4",
     "json5": "2.1.1",
     "lint-staged": "9.2.5",
     "node-fetch": "2.6.0",
+    "npm-package-arg": "6.1.0",
     "prettier": "1.18.2"
   },
   "scripts": {
@@ -36,7 +38,7 @@
     "publish-from-github": "./utils/publish.sh",
     "changelog": "node utils/changelog.js",
     "build": "node utils/run.js build all",
-    "test-lint": "node utils/run.js test-lint",
+    "now-build": "mkdir -p public && echo '<a href=\"https://vercel.com/import\">Import</a>' > public/output.html",
     "test-unit": "node utils/run.js test-unit",
     "test-integration-cli": "node utils/run.js test-integration-cli",
     "test-integration-once": "node utils/run.js test-integration-once",
@@ -71,6 +73,9 @@
       "sourceType": "module",
       "modules": true
     },
+    "plugins": [
+      "jest"
+    ],
     "extends": [
       "eslint:recommended",
       "plugin:@typescript-eslint/eslint-recommended",
@@ -89,8 +94,12 @@
       "@typescript-eslint/camelcase": 0,
       "@typescript-eslint/explicit-function-return-type": 0,
       "@typescript-eslint/no-empty-function": 0,
+      "@typescript-eslint/no-explicit-any": 0,
+      "@typescript-eslint/no-non-null-assertion": 0,
       "@typescript-eslint/no-unused-vars": 2,
-      "@typescript-eslint/no-use-before-define": 0
+      "@typescript-eslint/no-use-before-define": 0,
+      "jest/no-disabled-tests": 2,
+      "jest/no-focused-tests": 2
     },
     "overrides": [
       {

packages/frameworks/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "@now/frameworks",
-  "version": "0.0.13",
+  "name": "@vercel/frameworks",
+  "version": "0.0.14",
   "main": "frameworks.json",
   "license": "UNLICENSED"
 }

packages/now-build-utils/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "@now/build-utils",
-  "version": "2.2.1",
+  "name": "@vercel/build-utils",
+  "version": "2.3.0",
   "license": "MIT",
   "main": "./dist/index.js",
   "types": "./dist/index.d.js",
@@ -12,8 +12,8 @@
   },
   "scripts": {
     "build": "./build.sh",
-    "test-unit": "jest --env node --verbose --runInBand test/unit.*test.*",
-    "test-integration-once": "jest --env node --verbose --runInBand test/integration.test.js",
+    "test-unit": "jest --env node --verbose --runInBand --bail test/unit.*test.*",
+    "test-integration-once": "jest --env node --verbose --runInBand --bail test/integration.test.js",
     "prepublishOnly": "./build.sh"
   },
   "devDependencies": {

packages/now-build-utils/src/debug.ts

@@ -1,5 +1,7 @@
+import { getPlatformEnv } from './';
+
 export default function debug(message: string, ...additional: any[]) {
-  if (process.env.NOW_BUILDER_DEBUG) {
+  if (getPlatformEnv('BUILDER_DEBUG')) {
     console.log(message, ...additional);
   }
 }

packages/now-build-utils/src/detect-builders.ts

@@ -1,8 +1,9 @@
 import minimatch from 'minimatch';
 import { valid as validSemver } from 'semver';
 import { parse as parsePath, extname } from 'path';
-import { Route, Source } from '@now/routing-utils';
+import { Route, Source } from '@vercel/routing-utils';
 import { PackageJson, Builder, Config, BuilderFunctions } from './types';
+import { isOfficialRuntime } from './';
 
 interface ErrorResponse {
   code: string;
@@ -55,7 +56,7 @@ export function detectApiDirectory(builders: Builder[]): string | null {
 function getPublicBuilder(builders: Builder[]): Builder | null {
   const builder = builders.find(
     builder =>
-      builder.use === '@now/static' &&
+      isOfficialRuntime('static', builder.use) &&
       /^.*\/\*\*\/\*$/.test(builder.src) &&
       builder.config &&
       builder.config.zeroConfig === true
@@ -194,7 +195,8 @@ export async function detectBuilders(
       !fallbackEntrypoint &&
       buildCommand &&
       !fileName.includes('/') &&
-      fileName !== 'now.json'
+      fileName !== 'now.json' &&
+      fileName !== 'vercel.json'
     ) {
       fallbackEntrypoint = fileName;
     }
@@ -488,7 +490,7 @@ function getMissingBuildScriptError() {
     code: 'missing_build_script',
     message:
       'Your `package.json` file is missing a `build` property inside the `scripts` property.' +
-      '\nMore details: https://zeit.co/docs/v2/platform/frequently-asked-questions#missing-build-script',
+      '\nMore details: https://vercel.com/docs/v2/platform/frequently-asked-questions#missing-build-script',
   };
 }
 
@@ -593,7 +595,7 @@ function checkUnusedFunctions(
   }
 
   // Next.js can use functions only for `src/pages` or `pages`
-  if (frontendBuilder && frontendBuilder.use.startsWith('@now/next')) {
+  if (frontendBuilder && isOfficialRuntime('next', frontendBuilder.use)) {
     for (const fnKey of unusedFunctions.values()) {
       if (fnKey.startsWith('pages/') || fnKey.startsWith('src/pages')) {
         unusedFunctions.delete(fnKey);
@@ -958,7 +960,7 @@ function getRouteResult(
     outputDirectory &&
     frontendBuilder &&
     !options.featHandleMiss &&
-    frontendBuilder.use === '@now/static'
+    isOfficialRuntime('static', frontendBuilder.use)
   ) {
     defaultRoutes.push({
       src: '/(.*)',

packages/now-build-utils/src/detect-framework.ts

@@ -1,4 +1,4 @@
-import { Framework, FrameworkDetectionItem } from '@now/frameworks';
+import { Framework, FrameworkDetectionItem } from '@vercel/frameworks';
 import { DetectorFilesystem } from './detectors/filesystem';
 
 export interface DetectFrameworkOptions {

packages/now-build-utils/src/errors.ts

@@ -23,11 +23,11 @@ interface Props {
   message: string;
   /**
    * A unique error code for this particular error.
-   * Should start with the builder name such as `NOW_NODE_`.
+   * Should start with the builder name such as `NODE_`.
    */
   code: string;
   /**
-   * Optional hyperlink starting with https://zeit.co to
+   * Optional hyperlink starting with https://vercel.com to
    * link to more information about this error.
    */
   link?: string;

packages/now-build-utils/src/fs/node-version.ts

@@ -54,9 +54,9 @@ export async function getSupportedNodeVersion(
             engineRange +
             '".';
       throw new NowBuildError({
-        code: 'NOW_BUILD_UTILS_NODE_VERSION_INVALID',
+        code: 'BUILD_UTILS_NODE_VERSION_INVALID',
         link:
-          'https://zeit.co/docs/runtimes#official-runtimes/node-js/node-js-version',
+          'https://vercel.com/docs/runtimes#official-runtimes/node-js/node-js-version',
         message: intro + '\n' + pleaseSet,
       });
     }
@@ -72,9 +72,9 @@ export async function getSupportedNodeVersion(
           engineRange +
           '".';
     throw new NowBuildError({
-      code: 'NOW_BUILD_UTILS_NODE_VERSION_DISCONTINUED',
+      code: 'BUILD_UTILS_NODE_VERSION_DISCONTINUED',
       link:
-        'https://zeit.co/docs/runtimes#official-runtimes/node-js/node-js-version',
+        'https://vercel.com/docs/runtimes#official-runtimes/node-js/node-js-version',
       message: intro + '\n' + pleaseSet + '\n' + upstreamProvider,
     });
   }

packages/now-build-utils/src/fs/run-user-scripts.ts

@@ -39,7 +39,7 @@ export function spawnAsync(
         : 'Command';
       reject(
         new NowBuildError({
-          code: `NOW_BUILD_UTILS_SPAWN_${code || signal}`,
+          code: `BUILD_UTILS_SPAWN_${code || signal}`,
           message:
             opts.stdio === 'inherit'
               ? `${cmd} exited with ${code || signal}`
@@ -81,7 +81,7 @@ export function execAsync(
 
           return reject(
             new NowBuildError({
-              code: `NOW_BUILD_UTILS_EXEC_${code || signal}`,
+              code: `BUILD_UTILS_EXEC_${code || signal}`,
               message: `${cmd} exited with ${code || signal}`,
             })
           );
@@ -186,7 +186,8 @@ export async function getNodeVersion(
 async function scanParentDirs(destPath: string, readPackageJson = false) {
   assert(path.isAbsolute(destPath));
 
-  let hasPackageLockJson = false;
+  type CliType = 'yarn' | 'npm';
+  let cliType: CliType = 'yarn';
   let packageJson: PackageJson | undefined;
   let currentDestPath = destPath;
 
@@ -200,9 +201,13 @@ async function scanParentDirs(destPath: string, readPackageJson = false) {
         packageJson = JSON.parse(await fs.readFile(packageJsonPath, 'utf8'));
       }
       // eslint-disable-next-line no-await-in-loop
-      hasPackageLockJson = await fs.pathExists(
-        path.join(currentDestPath, 'package-lock.json')
-      );
+      const [hasPackageLockJson, hasYarnLock] = await Promise.all([
+        fs.pathExists(path.join(currentDestPath, 'package-lock.json')),
+        fs.pathExists(path.join(currentDestPath, 'yarn.lock')),
+      ]);
+      if (hasPackageLockJson && !hasYarnLock) {
+        cliType = 'npm';
+      }
       break;
     }
 
@@ -211,7 +216,7 @@ async function scanParentDirs(destPath: string, readPackageJson = false) {
     currentDestPath = newDestPath;
   }
 
-  return { hasPackageLockJson, packageJson };
+  return { cliType, packageJson };
 }
 
 interface WalkParentDirsProps {
@@ -268,7 +273,7 @@ export async function runNpmInstall(
   assert(path.isAbsolute(destPath));
   debug(`Installing to ${destPath}`);
 
-  const { hasPackageLockJson } = await scanParentDirs(destPath);
+  const { cliType } = await scanParentDirs(destPath);
   const opts: SpawnOptionsExtended = { cwd: destPath, ...spawnOpts };
   const env = opts.env ? { ...opts.env } : { ...process.env };
   delete env.NODE_ENV;
@@ -277,7 +282,7 @@ export async function runNpmInstall(
   let command: 'npm' | 'yarn';
   let commandArgs: string[];
 
-  if (hasPackageLockJson) {
+  if (cliType === 'npm') {
     opts.prettyCommand = 'npm install';
     command = 'npm';
     commandArgs = args
@@ -350,10 +355,7 @@ export async function runPackageJsonScript(
   spawnOpts?: SpawnOptions
 ) {
   assert(path.isAbsolute(destPath));
-  const { packageJson, hasPackageLockJson } = await scanParentDirs(
-    destPath,
-    true
-  );
+  const { packageJson, cliType } = await scanParentDirs(destPath, true);
   const hasScript = Boolean(
     packageJson &&
       packageJson.scripts &&
@@ -362,7 +364,7 @@ export async function runPackageJsonScript(
   );
   if (!hasScript) return false;
 
-  if (hasPackageLockJson) {
+  if (cliType === 'npm') {
     const prettyCommand = `npm run ${scriptName}`;
     console.log(`Running "${prettyCommand}"`);
     await spawnAsync('npm', ['run', scriptName], {

packages/now-build-utils/src/index.ts

@@ -80,3 +80,29 @@ export { readConfigFile } from './fs/read-config-file';
 export * from './schemas';
 export * from './types';
 export * from './errors';
+
+/**
+ * Helper function to support both `@vercel` and legacy `@now` official Runtimes.
+ */
+export const isOfficialRuntime = (desired: string, name?: string): boolean => {
+  if (typeof name !== 'string') {
+    return false;
+  }
+  return (
+    name === `@vercel/${desired}` ||
+    name === `@now/${desired}` ||
+    name.startsWith(`@vercel/${desired}@`) ||
+    name.startsWith(`@now/${desired}@`)
+  );
+};
+
+export const isStaticRuntime = (name?: string): boolean => {
+  return isOfficialRuntime('static', name);
+};
+
+/**
+ * Helper function to support both `VERCEL_` and legacy `NOW_` env vars.
+ */
+export const getPlatformEnv = (name: string): string | undefined => {
+  return process.env[`VERCEL_${name}`] || process.env[`NOW_${name}`];
+};

packages/now-build-utils/src/types.ts

@@ -49,8 +49,9 @@ export interface Config {
 
 export interface Meta {
   isDev?: boolean;
+  devCacheDir?: string;
   skipDownload?: boolean;
-  requestPath?: string;
+  requestPath?: string | null;
   filesChanged?: string[];
   filesRemoved?: string[];
   env?: Env;
@@ -81,7 +82,7 @@ export interface AnalyzeOptions {
 
   /**
    * An arbitrary object passed by the user in the build definition defined
-   * in `now.json`.
+   * in `vercel.json`.
    */
   config: Config;
 }
@@ -108,7 +109,7 @@ export interface BuildOptions {
 
   /**
    * An arbitrary object passed by the user in the build definition defined
-   * in `now.json`.
+   * in `vercel.json`.
    */
   config: Config;
 
@@ -148,7 +149,7 @@ export interface PrepareCacheOptions {
 
   /**
    * An arbitrary object passed by the user in the build definition defined
-   * in `now.json`.
+   * in `vercel.json`.
    */
   config: Config;
 }
@@ -182,11 +183,31 @@ export interface ShouldServeOptions {
 
   /**
    * An arbitrary object passed by the user in the build definition defined
-   * in `now.json`.
+   * in `vercel.json`.
    */
   config: Config;
 }
 
+export interface StartDevServerSuccess {
+  /**
+   * Port number where the dev server can be connected to, assumed to be running
+   * on `localhost`.
+   */
+  port: number;
+
+  /**
+   * Process ID number of the dev server. Useful for the `now dev` server to
+   * shut down the dev server once an HTTP request has been fulfilled.
+   */
+  pid: number;
+}
+
+/**
+ * `startDevServer()` may return `null` to opt-out of spawning a dev server for
+ * a given `entrypoint`.
+ */
+export type StartDevServerResult = StartDevServerSuccess | null;
+
 /**
  * Credit to Iain Reid, MIT license.
  * Source: https://gist.github.com/iainreid820/5c1cc527fe6b5b7dba41fec7fe54bf6e
@@ -315,24 +336,3 @@ export interface BuilderFunctions {
     excludeFiles?: string;
   };
 }
-
-export interface NowRewrite {
-  source: string;
-  destination: string;
-}
-
-export interface NowRedirect {
-  source: string;
-  destination: string;
-  statusCode?: number;
-}
-
-export interface NowHeader {
-  source: string;
-  headers: NowHeaderKeyValue[];
-}
-
-export interface NowHeaderKeyValue {
-  key: string;
-  value: string;
-}

packages/now-build-utils/test/fixtures/07-cross-install/now.json

@@ -1,6 +1,6 @@
 {
   "version": 2,
-  "builds": [{ "src": "api/index.js", "use": "@now/node" }],
+  "builds": [{ "src": "api/index.js", "use": "@vercel/node" }],
   "probes": [
     {
       "path": "/api/index.js",

packages/now-build-utils/test/fixtures/08-yarn-npm/now.json

@@ -1,11 +1,16 @@
 {
   "version": 2,
   "builds": [
-    { "src": "with-npm/index.js", "use": "@now/node" },
-    { "src": "with-yarn/index.js", "use": "@now/node" }
+    { "src": "with-npm/index.js", "use": "@vercel/node" },
+    { "src": "with-yarn/index.js", "use": "@vercel/node" },
+    { "src": "with-yarn-and-npm/index.js", "use": "@vercel/node" }
   ],
   "probes": [
     { "path": "/with-npm", "mustContain": "npm:RANDOMNESS_PLACEHOLDER" },
-    { "path": "/with-yarn", "mustContain": "yarn:RANDOMNESS_PLACEHOLDER" }
+    { "path": "/with-yarn", "mustContain": "yarn:RANDOMNESS_PLACEHOLDER" },
+    {
+      "path": "/with-yarn-and-npm",
+      "mustContain": "yarn:RANDOMNESS_PLACEHOLDER"
+    }
   ]
 }

packages/now-build-utils/test/fixtures/08-yarn-npm/with-yarn-and-npm/must-be-yarn.js

@@ -0,0 +1,14 @@
+const fs = require('fs');
+const path = require('path');
+
+const execpath = path.basename(process.env.npm_execpath);
+console.log('execpath', execpath);
+
+if (execpath === 'yarn.js' || execpath === 'yarn') {
+  fs.writeFileSync(
+    'index.js',
+    'module.exports = (_, resp) => resp.end("yarn:RANDOMNESS_PLACEHOLDER");'
+  );
+} else {
+  throw new Error('yarn is expected');
+}

packages/now-build-utils/test/fixtures/08-yarn-npm/with-yarn-and-npm/package-lock.json

@@ -0,0 +1,3 @@
+{
+  "lockfileVersion": 1
+}

packages/now-build-utils/test/fixtures/08-yarn-npm/with-yarn-and-npm/package.json

@@ -0,0 +1,5 @@
+{
+  "scripts": {
+    "now-build": "node must-be-yarn.js"
+  }
+}

packages/now-build-utils/test/fixtures/08-yarn-npm/with-yarn-and-npm/yarn.lock

@@ -0,0 +1,3 @@
+# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
+# yarn lockfile v1
+

packages/now-build-utils/test/fixtures/15-yarn-ignore-engines/now.json

@@ -3,7 +3,7 @@
   "builds": [
     {
       "src": "index.js",
-      "use": "@now/node"
+      "use": "@vercel/node"
     }
   ],
   "probes": [{ "path": "/", "mustContain": "found:RANDOMNESS_PLACEHOLDER" }]

packages/now-build-utils/test/fixtures/16-node-env-install/now.json

@@ -1,6 +1,6 @@
 {
   "version": 2,
-  "builds": [{ "src": "package.json", "use": "@now/static-build" }],
+  "builds": [{ "src": "package.json", "use": "@vercel/static-build" }],
   "build": { "env": { "NODE_ENV": "production" } },
   "probes": [{ "path": "/", "mustContain": "node-env:RANDOMNESS_PLACEHOLDER" }]
 }

packages/now-build-utils/test/fixtures/17-node-env-build/now.json

@@ -1,6 +1,6 @@
 {
   "version": 2,
-  "builds": [{ "src": "package.json", "use": "@now/static-build" }],
+  "builds": [{ "src": "package.json", "use": "@vercel/static-build" }],
   "build": { "env": { "NODE_ENV": "custom-value:RANDOMNESS_PLACEHOLDER" } },
   "probes": [
     { "path": "/", "mustContain": "custom-value:RANDOMNESS_PLACEHOLDER" }

packages/now-build-utils/test/fixtures/18-install-only-production/now.json

@@ -2,8 +2,8 @@
   "version": 2,
   "build": { "env": { "NPM_ONLY_PRODUCTION": "1" } },
   "builds": [
-    { "src": "npm/package.json", "use": "@now/static-build" },
-    { "src": "yarn/package.json", "use": "@now/static-build" }
+    { "src": "npm/package.json", "use": "@vercel/static-build" },
+    { "src": "yarn/package.json", "use": "@vercel/static-build" }
   ],
   "probes": [
     { "path": "/npm", "mustContain": "npm-prod:RANDOMNESS_PLACEHOLDER" },

packages/now-build-utils/test/integration.test.js

@@ -27,7 +27,7 @@ for (const fixture of fs.readdirSync(fixturesPath)) {
   }
 
   // eslint-disable-next-line no-loop-func
-  it(`should build ${fixture}`, async () => {
+  it(`Should build "${fixture}"`, async () => {
     await expect(
       testDeployment(
         { builderUrl, buildUtilsUrl },
@@ -53,7 +53,7 @@ for (const builder of buildersToTestWith) {
     // don't run all foreign fixtures, just some
     if (['01-cowsay', '01-cache-headers', '03-env-vars'].includes(fixture)) {
       // eslint-disable-next-line no-loop-func
-      it(`should build ${builder}/${fixture}`, async () => {
+      it(`Should build "${builder}/${fixture}"`, async () => {
         await expect(
           testDeployment(
             { builderUrl, buildUtilsUrl },
@@ -113,15 +113,13 @@ it('Test `detectBuilders` and `detectRoutes`', async () => {
   const { builders, defaultRoutes } = await detectBuilders(files, pkg);
 
   const nowConfig = { builds: builders, routes: defaultRoutes, probes };
+
   await fs.writeFile(
     path.join(fixture, 'now.json'),
     JSON.stringify(nowConfig, null, 2)
   );
 
-  const deployment = await testDeployment(
-    { builderUrl, buildUtilsUrl },
-    fixture
-  );
+  const deployment = await testDeployment({ builderUrl }, fixture);
   expect(deployment).toBeDefined();
 });
 
@@ -199,9 +197,6 @@ it('Test `detectBuilders` with `index` files', async () => {
     JSON.stringify(nowConfig, null, 2)
   );
 
-  const deployment = await testDeployment(
-    { builderUrl, buildUtilsUrl },
-    fixture
-  );
+  const deployment = await testDeployment({ builderUrl }, fixture);
   expect(deployment).toBeDefined();
 });