Publish Canary

- @vercel/frameworks@0.0.15-canary.0
 - @vercel/build-utils@2.3.2-canary.1
 - vercel@19.0.2-canary.3
 - @vercel/node@1.6.2-canary.1

.changeset/README.md

@@ -1,8 +0,0 @@
-# Changesets
-
-Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
-with multi-package repos, or single-package repos to help you version and publish your code. You can
-find the full documentation for it [in our repository](https://github.com/changesets/changesets)
-
-We have a quick list of common questions to get you started engaging with this project in
-[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -1,14 +0,0 @@
-{
-  "$schema": "https://unpkg.com/@changesets/config@2.3.0/schema.json",
-  "changelog": [
-    "@svitejs/changesets-changelog-github-compact",
-    { "repo": "vercel/vercel" }
-  ],
-  "commit": false,
-  "fixed": [],
-  "linked": [],
-  "access": "public",
-  "baseBranch": "main",
-  "updateInternalDependencies": "patch",
-  "ignore": []
-}

.editorconfig

@@ -19,11 +19,6 @@ indent_style = space
 [*.py]
 indent_size = 4
 
-[*.go]
-indent_style = tab
-indent_size = 4
-tab_width = 4
-
 [*.asm]
 indent_size = 8
 

.eslintignore

@@ -2,43 +2,35 @@ node_modules
 dist
 examples
 
-packages/node/src/bridge.ts
+# gatsby-plugin-now
+packages/gatsby-plugin-now/test/fixtures
 
-packages/*/test/fixtures
+# now-build-utils
+packages/now-build-utils/test/fixtures
 
-# cli
-packages/cli/@types
-packages/cli/download
-packages/cli/dist
-packages/cli/test/dev/fixtures
-packages/cli/bin
-packages/cli/link
-packages/cli/src/util/dev/templates/*.ts
+# now-cli
+packages/now-cli/@types
+packages/now-cli/download
+packages/now-cli/dist
+packages/now-cli/test/fixtures
+packages/now-cli/test/dev/fixtures
+packages/now-cli/bin
+packages/now-cli/link
+packages/now-cli/src/util/dev/templates/*.ts
 
-# client
-packages/client/tests/fixtures
-packages/client/lib
+# now-client
+packages/now-client/tests/fixtures
+packages/now-client/lib
 
-# hydrogen
-packages/hydrogen/edge-entry.js
+# now-next
+packages/now-next/test/fixtures
 
-# next
-packages/next/test/integration/middleware
-packages/next/test/integration/middleware-eval
+# now-node
+packages/now-node/src/bridge.ts
+packages/now-node/test/fixtures
 
-# middleware
-packages/middleware/src/entries.js
+# now-node-bridge
+packages/now-node-bridge/bridge.*
 
-# static-build
-packages/static-build/test/fixtures
-packages/static-build/test/build-fixtures
-packages/static-build/test/cache-fixtures
-
-# redwood
-packages/redwood/test/fixtures
-
-# remix
-packages/remix/test/fixtures
-
-# gatsby-plugin-vercel-analytics
-packages/gatsby-plugin-vercel-analytics
+# now-static-build
+packages/now-static-build/test/fixtures

.gitattributes

@@ -8,7 +8,3 @@ packages/*/test/* linguist-vendored
 # Go build fails with Windows line endings.
 *.go text eol=lf
 go.mod text eol=lf
-
-# Mark certain files as "binary" -- hide diffs
-**/test/fixtures/**/git/**/* binary
-**/test/fixtures/**/git/**/* linguist-generated

.github/CODEOWNERS

@@ -1,18 +1,27 @@
 # Documentation
 # https://help.github.com/en/articles/about-code-owners
 
-# Restricted Paths
-*                                        @TooTallNate @EndangeredMassa @trek
-/.github/workflows                       @TooTallNate @EndangeredMassa @trek @ijjk
-/packages/fs-detectors                   @TooTallNate @EndangeredMassa @trek @agadzik @chloetedder
-/packages/next                           @TooTallNate @EndangeredMassa @Ethan-Arrowood @trek @ijjk @ztanner
-/packages/routing-utils                  @TooTallNate @EndangeredMassa @trek @ijjk
-/packages/static-build                   @TooTallNate @EndangeredMassa @trek
-/packages/edge                           @vercel/compute @TooTallNate @EndangeredMassa @trek
-/examples                                @leerob
+*                                        @tootallnate
+/.github/workflows                       @AndyBitz @styfle
+/packages/frameworks                     @AndyBitz
+/packages/now-cli/src/commands/dev/      @tootallnate @styfle @AndyBitz
+/packages/now-cli/src/util/dev/          @tootallnate @styfle @AndyBitz
+/packages/now-cli/src/commands/domains/  @javivelasco @mglagola @anatrajkovska
+/packages/now-cli/src/commands/certs/    @javivelasco @mglagola @anatrajkovska
+/packages/now-cli/src/commands/env       @styfle @lucleray
+/packages/now-client                     @rdev
+/packages/now-build-utils                @styfle @AndyBitz
+/packages/now-node                       @styfle @tootallnate @lucleray
+/packages/now-node-bridge                @styfle @tootallnate @lucleray
+/packages/now-next                       @Timer @ijjk
+/packages/now-go                         @styfle @sophearak
+/packages/now-python                     @styfle @sophearak
+/packages/now-ruby                       @styfle @coetry @nathancahill
+/packages/now-static-build               @styfle @AndyBitz
+/packages/now-routing-utils              @styfle @dav-is @ijjk
+/examples                                @msweeneydev @timothyis
 /examples/create-react-app               @Timer
-/examples/nextjs                         @timneutkens @ijjk @ztanner @huozhi
-/packages/node                           @TooTallNate @EndangeredMassa @trek @Kikobeats
-
-# Unrestricted Paths
-.changeset/
+/examples/nextjs                         @timneutkens
+/examples/hugo                           @msweeneydev @timothyis @styfle
+/examples/jekyll                         @msweeneydev @timothyis @sarupbanskota
+/examples/zola                           @msweeneydev @timothyis @styfle

.github/CONTRIBUTING.md

@@ -1,44 +1,32 @@
 # Contributing
 
-When contributing to this repository, please first discuss the change you wish to make via [GitHub Discussions](https://github.com/vercel/vercel/discussions/new) with the owners of this repository before submitting a Pull Request.
+When contributing to this repository, please first discuss the change you wish to make via [GitHub Discussions](https://github.com/zeit/now/discussions/new) with the owners of this repository before submitting a Pull Request.
 
-Please read our [Code of Conduct](CODE_OF_CONDUCT.md) and follow it in all your interactions with the project.
+Please read our [code of conduct](CODE_OF_CONDUCT.md) and follow it in all your interactions with the project.
 
 ## Local development
 
-This project is configured in a monorepo, where one repository contains multiple npm packages. Dependencies are installed and managed with `pnpm`, not `npm` CLI.
+This project is configured in a monorepo pattern where one repo contains multiple npm packages. Dependencies are installed and managed with `yarn`, not `npm` CLI.
 
 To get started, execute the following:
 
 ```
-git clone https://github.com/vercel/vercel
-cd vercel
-corepack enable
-pnpm install
-pnpm build
-pnpm lint
-pnpm test-unit
+git clone https://github.com/zeit/now
+yarn install
+yarn bootstrap
+yarn build
+yarn lint
+yarn test
 ```
 
 Make sure all the tests pass before making changes.
 
-### Running Vercel CLI Changes
-
-You can use `pnpm dev` from the `cli` package to invoke Vercel CLI with local changes:
-
-```
-cd ./packages/cli
-pnpm dev <cli-commands...>
-```
-
-See [CLI Local Development](../packages/cli#local-development) for more details.
-
 ## Verifying your change
 
-Once you are done with your changes (we even suggest doing it along the way), make sure all the tests still pass by running:
+Once you are done with your changes (we even suggest doing it along the way ), make sure all the test still run by running
 
 ```
-pnpm test-unit
+yarn build && yarn test
 ```
 
 from the root of the project.
@@ -62,7 +50,7 @@ Unit tests are run locally with `jest` and execute quickly because they are test
 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.vercel.app/root.js does not contain hello Root!. Instead it contains An error occurred with this application.
+[Error: Fetched page https://test-8ashcdlew.now.sh/root.js does not contain hello Root!. Instead it contains An error occurred with this application.
 
     NO_STATUS_CODE_FRO Response headers:
        cache-control=s-maxage=0
@@ -76,17 +64,17 @@ Integration tests create deployments to your Vercel account using the `test` pro
       x-now-trace=iad1]
 ```
 
-In such cases, you can visit the URL of the failed deployment and append `/_logs` to see the build error. In the case above, that would be https://test-8ashcdlew.vercel.app/_logs
+In such cases you can visit the URL of the failed deployment and append `/_logs` so see the build error. In the case above, that would be https://test-8ashcdlew.now.sh/_logs
 
 The logs of this deployment will contain the actual error which may help you to understand what went wrong.
 
-### @vercel/nft
+### @zeit/node-file-trace
 
-Some of the Builders use `@vercel/nft` to tree-shake files before deployment. If you suspect an error with this tree-shaking mechanism, you can create the following script in your project:
+Some of the Builders use `@zeit/node-file-trace` to tree-shake files before deployment. If you suspect an error with this tree-shaking mechanism, you can create the following script in your project:
 
 ```js
-const { nodeFileTrace } = require('@vercel/nft');
-nodeFileTrace(['path/to/entrypoint.js'], {
+const trace = require('@zeit/node-file-trace');
+trace(['path/to/entrypoint.js'], {
   ts: true,
   mixedModules: true,
 })
@@ -94,15 +82,24 @@ nodeFileTrace(['path/to/entrypoint.js'], {
   .then(e => console.error(e));
 ```
 
-When you run this script, you'll see all the imported files. If anything file is missing, the bug is in [@vercel/nft](https://github.com/vercel/nft) and not the Builder.
+When you run this script, you'll see all imported files. If anything file is missing, the bug is in [@zeit/node-file-trace](https://github.com/zeit/node-file-trace) and not the Builder.
 
 ## Deploy a Builder with existing project
 
-Sometimes you want to test changes to a Builder against an existing project, maybe with `vercel dev` or actual deployment. You can avoid publishing every Builder change to npm by uploading the Builder as a tarball.
+Sometimes you want to test changes to a Builder against an existing project, maybe with `now dev` or an actual deployment. You can avoid publishing every Builder change to npm by uploading the Builder as a tarball.
 
-1. Change directory to the desired Builder `cd ./packages/node`
-2. Run `pnpm build` to compile typescript and other build steps
+1. Change directory to the desired Builder `cd ./packages/now-node`
+2. Run `yarn build` to compile typescript and other build steps
 3. Run `npm pack` to create a tarball file
-4. Run `vercel *.tgz` to upload the tarball file and get a URL
+4. Run `now *.tgz` to upload the tarball file and get a URL
 5. Edit any existing `vercel.json` project and replace `use` with the URL
-6. Run `vercel` or `vercel dev` to deploy with the experimental Builder
+6. Run `now` or `now dev` to deploy with the experimental Builder
+
+## Add a New Framework
+
+You can add support for a new Framework by creating a Pull Request for this repository and following the steps below:
+
+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 Vercel dashboard and deploy it.

.github/DISCUSSION_TEMPLATE/general.yml

@@ -1,12 +0,0 @@
-body:
-  - type: markdown
-    attributes:
-      value: |
-        **Note**: This category is intended for discussions related to Vercel CLI or Runtimes. 
-
-        If you post in this repository seeking help with other Vercel tools and features, it may be missed by our support team. For help with topics other than the CLI and Runtimes, please visit the [Vercel Community](https://github.com/orgs/vercel/discussions).
-  - type: textarea
-    attributes:
-      label: Description
-    validations:
-      required: true

.github/DISCUSSION_TEMPLATE/help.yml

@@ -1,12 +0,0 @@
-body:
-  - type: markdown
-    attributes:
-      value: |
-        **Note**: This category is intended for discussions related to Vercel CLI or Runtimes. 
-
-        If you post in this repository seeking help with other Vercel tools and features, it may be missed by our support team. For help with topics other than the CLI and Runtimes, please visit the [Vercel Community](https://github.com/orgs/vercel/discussions).
-  - type: textarea
-    attributes:
-      label: Question
-    validations:
-      required: true

.github/DISCUSSION_TEMPLATE/ideas.yml

@@ -1,12 +0,0 @@
-body:
-  - type: markdown
-    attributes:
-      value: |
-        **Note**: This category is intended for sharing ideas related to Vercel CLI or Runtimes. 
-
-        Please visit the [Vercel Community](https://github.com/orgs/vercel/discussions) to share ideas for other Vercel tools and features.
-  - type: textarea
-    attributes:
-      label: Idea
-    validations:
-      required: true

.github/DISCUSSION_TEMPLATE/show-and-tell.yml

@@ -1,12 +0,0 @@
-body:
-  - type: markdown
-    attributes:
-      value: |
-        **Note**: This category is intended for discussions related to Vercel CLI or Runtimes. 
-
-        For topics related to other Vercel features, please visit the [Vercel Community](https://github.com/orgs/vercel/discussions).
-  - type: textarea
-    attributes:
-      label: Description
-    validations:
-      required: true

.github/EXAMPLE_README_TEMPLATE.md

@@ -1,19 +1,19 @@
 # [Name] Example
 
-This directory is a brief example of a [Name](site-link) site that can be deployed to Vercel with 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 Vercel.
 
-[![Deploy with Vercel](https://vercel.com/button)](https://vercel.com/new/clone?repository-url=https://github.com/vercel/vercel/tree/main/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 Vercel, you can use the [CLI Tool Used](CLI-link) to initialize the project:
 
 ```shell
-$ vercel init [Name]]
+$ now init charge
 ```
 
 ### Deploying From Your Terminal
@@ -21,5 +21,5 @@ $ vercel init [Name]]
 Once initialized, you can deploy the [Name] example with just a single command:
 
 ```shell
-$ vercel
+$ now
 ```

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
-blank_issues_enabled: true
+blank_issues_enabled: false
 contact_links:
   - name: Bug Report
-    url: https://vercel.com/help
-    about: Reach out to our support team
+    url: https://vercel.com/support/request
+    about: Report a bug using the Vercel support form
   - name: Feature Request
-    url: https://github.com/orgs/vercel/discussions/new?category=ideas
-    about: Share ideas for new features
+    url: https://github.com/zeit/now/discussions/new
+    about: Request a feature to be added to the platform
   - name: Ask a Question
-    url: https://github.com/orgs/vercel/discussions/new?category=help
-    about: Ask the community for help
+    url: https://github.com/zeit/now/discussions/new
+    about: Ask questions and discuss with other community members

.github/dependabot.yml

@@ -1,64 +0,0 @@
-version: 2
-
-updates:
-  - schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    directory: /packages/static-build/test/fixtures/angular-v17
-    allow:
-      - dependency-name: '@angular*'
-    groups:
-      core:
-        patterns:
-          - '@angular*'
-        update-types:
-          - 'minor'
-
-  - schedule:
-    interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    directory: /packages/static-build/test/fixtures/astro-v4
-    allow:
-      - dependency-name: 'astro*'
-    groups:
-      core:
-        patterns:
-          - 'astro*'
-        update-types:
-          - 'minor'
-
-  - schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    directory: /packages/static-build/test/fixtures/hydrogen-v2023
-    allow:
-      - dependency-name: '@remix-run*'
-      - dependency-name: '@shopify*'
-    groups:
-      core:
-        patterns:
-          - '@remix-run*'
-          - '@shopify*'
-        update-types:
-          - 'minor'

.github/workflows/cancel.yml

@@ -0,0 +1,18 @@
+name: Cancel
+on:
+  push:
+    branches:
+    - '**'
+    - '!master'
+
+jobs:
+  cancel:
+    name: 'Cancel Previous Runs'
+    runs-on: ubuntu-latest
+    timeout-minutes: 3
+    steps:
+      - uses: styfle/cancel-workflow-action@0.3.1
+        with:
+          workflow_id: 849295, 849296, 849297, 849298
+          access_token: ${{ secrets.GITHUB_WORKFLOW_TOKEN }}
+

.github/workflows/cron-update-gatsby-fixtures.yml

@@ -1,34 +0,0 @@
-name: Cron Update Gatsby Fixtures
-
-on:
-  # Allow manual runs
-  workflow_dispatch:
-  # Run once a week https://crontab.guru/once-a-week
-  schedule:
-    - cron: '0 0 * * 0'
-
-jobs:
-  update-gatsby-fixtures:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-        # 0 means fetch all commits so we can commit and push in the script below
-        with:
-          fetch-depth: 0
-      - uses: actions/setup-node@v3
-        with:
-          node-version: 16
-      - name: Enable corepack
-        run: corepack enable pnpm
-      - name: Update Gatsby Fixtures
-        uses: actions/github-script@v6
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-        # See https://github.com/actions/github-script#run-a-separate-file-with-an-async-function
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/update-gatsby-fixtures.js')
-            await script({ github, context })

.github/workflows/cron-update-next.yml

@@ -1,31 +0,0 @@
-name: Cron Update Next
-
-on:
-  # Allow manual runs
-  workflow_dispatch:
-  # Run every 4 hours https://crontab.guru/every-4-hours
-  schedule:
-    - cron: '0 */4 * * *'
-
-jobs:
-  create-pull-request:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-        # 0 means fetch all commits so we can commit and push in the script below
-        with:
-          fetch-depth: 0
-      - name: Enable corepack
-        run: corepack enable pnpm
-      - name: Create Pull Request
-        uses: actions/github-script@v6
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-        # See https://github.com/actions/github-script#run-a-separate-file-with-an-async-function
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/update-next.js')
-            await script({ github, context })

.github/workflows/cron-update-turbo.yml

@@ -1,31 +0,0 @@
-name: Cron Update Turbo
-
-on:
-  # Allow manual runs
-  workflow_dispatch:
-  # Run every week https://crontab.guru/every-week
-  schedule:
-    - cron: '0 0 * * 0'
-
-jobs:
-  create-pull-request:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-        # 0 means fetch all commits so we can commit and push in the script below
-        with:
-          fetch-depth: 0
-      - name: Enable corepack
-        run: corepack enable pnpm
-      - name: Create Pull Request
-        uses: actions/github-script@v6
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-        # See https://github.com/actions/github-script#run-a-separate-file-with-an-async-function
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/update-turbo.js')
-            await script({ github, context })

.github/workflows/label-feature-request.yml

@@ -1,22 +0,0 @@
-name: 🤖 Issue labeler - Feature Request
-on:
-  issues:
-    types:
-      - labeled
-jobs:
-  add-comment:
-    if: "github.event.label.name == 'triaged: feature request'"
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-    steps:
-      - name: Add comment
-        uses: peter-evans/create-or-update-comment@5adcb0bb0f9fb3f95ef05400558bdb3f329ee808
-        with:
-          issue-number: ${{ github.event.issue.number }}
-          body: |
-            Thank you for taking the time to created this request!             
-
-            We added it to our backlog but need to discuss design/architecture before we can accept a PR. 
-
-            Please let us know if you would be interested in sending a PR once we approve the design.

.github/workflows/label-support.yml

@@ -1,24 +0,0 @@
-name: 🤖 Issue labeler - Support
-on:
-  issues:
-    types:
-      - labeled
-jobs:
-  add-comment:
-    if: github.event.label.name == 'support'
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-    steps:
-      - name: Add comment
-        uses: peter-evans/close-issue@v2
-        with:
-          issue-number: ${{ github.event.issue.number }}
-          comment: |
-            Thank you so much for filing this issue. 
-
-            We do try to keep issues in this repository focused on the vercel command line and related code. 
-
-            At this point we think that this issue is best handled by our friendly Vercel support team. They can be found by contacting them at: https://vercel.com/help#issues
-
-            If you think closing of this is a mistake, then please re-open this issue and we'll take another look :bow:

.github/workflows/label-triaged.yml

@@ -1,24 +0,0 @@
-name: 🤖 Issue labeler - Triaged
-on:
-  issues:
-    types:
-      - labeled
-jobs:
-  add-comment:
-    if: "github.event.label.name == 'triaged: bug'"
-    runs-on: ubuntu-latest
-    permissions:
-      issues: write
-    steps:
-      - name: Add comment
-        uses: peter-evans/create-or-update-comment@5adcb0bb0f9fb3f95ef05400558bdb3f329ee808
-        with:
-          issue-number: ${{ github.event.issue.number }}
-          body: |
-            Thank you for taking the time to file this issue!             
-
-            We have confirmed this is a bug and added it to our backlog.
-
-            We don't have a timeline for when this issue will be fixed, but we will accept a Pull Request with a fix and a test.
-
-            See the [contributing guidelines](https://github.com/vercel/vercel/blob/main/.github/CONTRIBUTING.md) for more info.

.github/workflows/publish.yml

@@ -0,0 +1,31 @@
+name: Publish
+
+on:
+  push:
+    branches:
+    - master
+    tags:
+    - '!*'
+
+jobs:
+  publish:
+    name: Publish
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v1
+    - uses: actions/setup-node@v1
+      with:
+        node-version: 10
+    - name: Install
+      run: yarn install --check-files --frozen-lockfile
+    - name: Build
+      run: yarn build
+      env:
+        GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
+        SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
+    - name: Publish
+      run: yarn publish-from-github
+      env:
+        NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
+        SENTRY_DSN: ${{ secrets.SENTRY_DSN }}

.github/workflows/release.yml

@@ -1,87 +0,0 @@
-name: Release
-
-on:
-  push:
-    branches:
-      - main
-
-env:
-  TURBO_REMOTE_ONLY: 'true'
-  TURBO_TEAM: 'vercel'
-  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-
-concurrency: ${{ github.workflow }}-${{ github.ref }}
-
-jobs:
-  release:
-    name: Release
-    runs-on: ubuntu-latest
-    permissions:
-      contents: write
-      id-token: write
-    steps:
-      - name: Checkout Repo
-        uses: actions/checkout@v3
-
-      - name: Fetch git tags
-        run: git fetch origin 'refs/tags/*:refs/tags/*'
-
-      - name: Setup Node
-        uses: actions/setup-node@v3
-        with:
-          node-version: 16
-
-      - name: install npm@9
-        run: npm i -g npm@9
-
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
-
-      - name: Install Dependencies
-        run: pnpm install --frozen-lockfile
-
-      - name: Build Packages
-        run: pnpm build
-        env:
-          GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-
-      - name: Create Release Pull Request or Publish to npm
-        id: changesets
-        uses: changesets/action@v1
-        with:
-          version: pnpm ci:version
-          publish: pnpm ci:publish
-        env:
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          NPM_CONFIG_PROVENANCE: 'true'
-          NPM_TOKEN: ${{ secrets.NPM_TOKEN_ELEVATED }}
-          GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
-          SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
-
-      - name: Trigger Update (if a Publish Happened)
-        if: steps.changesets.outputs.published == 'true'
-        uses: actions/github-script@v6
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/trigger-update-workflow.js')
-            await script({ github, context })
-
-      - name: Set latest Release to `vercel` (if a Publish Happened)
-        if: steps.changesets.outputs.published == 'true'
-        uses: actions/github-script@v6
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/update-latest-release.js')
-            await script({ github, context })
-  summary:
-    name: Summary
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    needs:
-      - release
-    steps:
-      - name: Check All
-        run: echo OK

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

@@ -0,0 +1,33 @@
+name: CLI
+
+on:
+  push:
+    branches:
+    - master
+    tags:
+    - '!*'
+  pull_request:
+
+jobs:
+  test:
+    name: CLI
+    timeout-minutes: 30
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest]
+        node: [10, 12]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v2
+      - run: git fetch origin master --depth=10
+      - run: git fetch origin ${{ github.ref }} --depth=10
+      - run: yarn install
+      - run: yarn run build
+      - uses: actions/setup-node@v1
+        with:
+          node-version: ${{ matrix.node }}
+      - run: yarn test-integration-cli --clean false
+        env:
+          ZEIT_TEAM_TOKEN: ${{ secrets.ZEIT_TEAM_TOKEN }}
+          ZEIT_REGISTRATION_URL: ${{ secrets.ZEIT_REGISTRATION_URL }}

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

@@ -0,0 +1,36 @@
+name: Dev
+
+on:
+  push:
+    branches:
+    - master
+    tags:
+    - '!*'
+  pull_request:
+
+jobs:
+  test:
+    name: Dev
+    timeout-minutes: 45
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+        node: [10, 12]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - 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
+        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-integration-once.yml

@@ -0,0 +1,25 @@
+name: E2E
+
+on:
+  push:
+    branches:
+    - master
+    tags:
+    - '!*'
+  pull_request:
+
+jobs:
+  test:
+    name: E2E
+    timeout-minutes: 120
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - run: git fetch origin master --depth=10
+      - run: git fetch origin ${{ github.ref }} --depth=10
+      - run: yarn install
+      - run: yarn run build
+      - run: yarn test-integration-once --clean false
+        env:
+          ZEIT_TEAM_TOKEN: ${{ secrets.ZEIT_TEAM_TOKEN }}
+          ZEIT_REGISTRATION_URL: ${{ secrets.ZEIT_REGISTRATION_URL }}

.github/workflows/test-lint.yml

@@ -1,54 +0,0 @@
-name: Lint
-
-on:
-  push:
-    branches:
-      - main
-    tags:
-      - '!*'
-  pull_request:
-
-env:
-  TURBO_REMOTE_ONLY: 'true'
-  TURBO_TEAM: 'vercel'
-  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-  NODE_VERSION: '16'
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  enforce-changeset:
-    name: Enforce Changeset
-    runs-on: ubuntu-latest
-    if: github.event_name == 'pull_request' && github.event.pull_request.title != 'Version Packages'
-    steps:
-      - uses: actions/checkout@v3
-        with:
-          fetch-depth: 0
-          ref: main
-      - run: git fetch origin ${{ github.event.pull_request.head.sha }}:pr-${{ github.event.pull_request.number }}
-      - run: git checkout pr-${{ github.event.pull_request.number }}
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
-      - run: pnpm install
-      # Enforce a changeset file to be present
-      - run: pnpm exec changeset status --since=main
-
-  test:
-    name: Lint
-    timeout-minutes: 10
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
-      - run: pnpm install
-      - run: pnpm run lint
-      - run: pnpm run prettier-check
-      - run: pnpm run build
-      - run: pnpm run type-check

.github/workflows/test-unit.yml

@@ -0,0 +1,34 @@
+name: Unit
+
+on:
+  push:
+    branches:
+    - master
+    tags:
+    - '!*'
+  pull_request:
+
+jobs:
+  test:
+    name: Unit
+    timeout-minutes: 15
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        node: [10, 12]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v2
+      - run: git fetch origin master --depth=10
+      - run: git fetch origin ${{ github.ref }} --depth=10
+      - uses: actions/setup-node@v1
+      - run: yarn install
+      - run: yarn run build
+      - 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 vercel run coverage
+        if: matrix.os == 'ubuntu-latest' && matrix.node == 12 # only run coverage once
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test.yml

@@ -1,134 +0,0 @@
-name: Tests
-
-on:
-  push:
-    branches:
-      - main
-    tags:
-      - '!*'
-  pull_request:
-
-env:
-  NODE_VERSION: '16'
-  TURBO_REMOTE_ONLY: 'true'
-  TURBO_TEAM: 'vercel'
-  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
-
-concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: ${{ github.ref != 'refs/heads/main' }}
-
-jobs:
-  setup:
-    name: Find Changes
-    runs-on: ubuntu-latest
-    outputs:
-      tests: ${{ steps['set-tests'].outputs['tests'] }}
-      dplUrl: ${{ steps.waitForTarball.outputs.url }}
-    steps:
-      - uses: actions/checkout@v3
-        with:
-          fetch-depth: 2
-      - uses: actions/setup-node@v3
-        with:
-          node-version: ${{ env.NODE_VERSION }}
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
-      - run: pnpm install
-      - id: set-tests
-        run: |
-          TESTS_ARRAY=$(node utils/chunk-tests.js $SCRIPT_NAME)
-          echo "Files to test:"
-          echo "$TESTS_ARRAY"
-          echo "tests=$TESTS_ARRAY" >> $GITHUB_OUTPUT
-      - uses: patrickedqvist/wait-for-vercel-preview@bfdff514ff78a669f2536e9f4dd4ef5813a704a2
-        id: waitForTarball
-        with:
-          token: ${{ secrets.GITHUB_TOKEN }}
-          max_timeout: 360
-          check_interval: 5
-  test:
-    timeout-minutes: 120
-    runs-on: ${{ matrix.runner }}
-    name: ${{matrix.scriptName}} (${{matrix.packageName}}, ${{matrix.chunkNumber}}, ${{ matrix.runner }})
-    if: ${{ needs.setup.outputs['tests'] != '[]' }}
-    needs:
-      - setup
-    strategy:
-      fail-fast: false
-      matrix:
-        include: ${{ fromJson(needs.setup.outputs['tests']) }}
-    steps:
-      - uses: actions/checkout@v3
-        with:
-          fetch-depth: 2
-      - uses: actions/setup-node@v3
-        with:
-          node-version: ${{ matrix.nodeVersion || env.NODE_VERSION }}
-
-      - name: Install Hugo
-        if: matrix.runner == '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/cli/test/dev/fixtures/08-hugo/
-
-      # yarn 1.22.21 introduced a Corepack bug when running tests.
-      # this can be removed once https://github.com/yarnpkg/yarn/issues/9015 is resolved
-      - name: install yarn@1.22.19
-        run: npm i -g yarn@1.22.19
-
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
-
-      - run: pnpm install
-      - name: fetch ssl certificate before build (linux, os x)
-        if: matrix.runner != 'windows-latest'
-        run: echo | openssl s_client -showcerts -servername 'api.vercel.com' -connect 76.76.21.21:443
-
-      - name: Build ${{matrix.packageName}} and all its dependencies
-        run: node utils/gen.js && node_modules/.bin/turbo run build --cache-dir=".turbo" --log-order=stream --scope=${{matrix.packageName}} --include-dependencies --no-deps
-        env:
-          FORCE_COLOR: '1'
-      - name: Test ${{matrix.packageName}}
-        run: node utils/gen.js && node_modules/.bin/turbo run test --summarize --cache-dir=".turbo" --log-order=stream --scope=${{matrix.packageName}} --no-deps -- ${{ join(matrix.testPaths, ' ') }}
-        shell: bash
-        env:
-          JEST_JUNIT_OUTPUT_FILE: ${{github.workspace}}/.junit-reports/${{matrix.scriptName}}-${{matrix.packageName}}-${{matrix.chunkNumber}}-${{ matrix.runner }}.xml
-          VERCEL_CLI_VERSION: ${{ needs.setup.outputs.dplUrl }}/tarballs/vercel.tgz
-          VERCEL_TEST_TOKEN: ${{ secrets.VERCEL_TEST_TOKEN }}
-          VERCEL_TEST_REGISTRATION_URL: ${{ secrets.VERCEL_TEST_REGISTRATION_URL }}
-          FORCE_COLOR: '1'
-      - name: 'Determine Turbo HIT or MISS'
-        if: ${{ !cancelled() }}
-        id: turbo-summary
-        shell: bash
-        run: |
-          TURBO_MISS_COUNT=`node utils/determine-turbo-hit-or-miss.js`
-          echo "MISS COUNT: $TURBO_MISS_COUNT"
-          echo "misses=$TURBO_MISS_COUNT" >> $GITHUB_OUTPUT
-      - name: fetch ssl certificate after tests (linux, os x)
-        if: matrix.runner != 'windows-latest'
-        run: echo | openssl s_client -showcerts -servername 'api.vercel.com' -connect 76.76.21.21:443
-      - name: 'Upload Test Report to Datadog'
-        if: ${{ steps['turbo-summary'].outputs.misses != '0' && !cancelled() }}
-        run: 'npx @datadog/datadog-ci@2.18.1 junit upload --service vercel-cli .junit-reports'
-        env:
-          DATADOG_API_KEY: ${{secrets.DATADOG_API_KEY_CLI}}
-          DD_ENV: ci
-
-  summary:
-    name: Summary
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    if: always()
-    needs:
-      - test
-    steps:
-      - name: Check All
-        run: |-
-          for status in ${{ join(needs.*.result, ' ') }}
-          do
-            if [ "$status" != "success" ] && [ "$status" != "skipped" ]
-            then
-              echo "Some checks failed"
-              exit 1
-            fi
-          done

.github/workflows/update-remix-run-dev.yml

@@ -1,30 +0,0 @@
-name: Update @remix-run/dev
-
-on:
-  workflow_dispatch:
-    inputs:
-      new-version:
-        type: string
-        description: 'Optional version to update @remix-run/dev to inside of @vercel/remix-builder'
-
-jobs:
-  update-remix-run-dev:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v3
-        with:
-          fetch-depth: 0
-      - name: Setup node
-        uses: actions/setup-node@v3
-        with:
-          node-version: 16
-      - name: Enable corepack
-        run: corepack enable pnpm
-      - name: Update @remix-run/dev
-        uses: actions/github-script@v6
-        with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
-          script: |
-            const script = require('./utils/update-remix-run-dev.js')
-            await script({ github, context }, "${{ inputs.new-version }}")

.gitignore

@@ -1,4 +1,5 @@
 node_modules
+package-lock.json
 dist
 .vscode
 npm-debug.log
@@ -9,26 +10,20 @@ coverage.lcov
 *.swp
 *.bak
 *.tgz
-packages/cli/src/util/dev/templates/*.ts
-packages/cli/src/util/constants.ts
-packages/cli/test/**/yarn.lock
-!packages/cli/test/dev/**/yarn.lock
-packages/cli/test/**/node_modules
-packages/cli/test/dev/fixtures/08-hugo/hugo
-packages/cli/test/dev/fixtures/**/dist
-packages/cli/test/dev/fixtures/**/public
-packages/cli/test/dev/fixtures/**/.now
-packages/cli/test/dev/fixtures/**/.vercel
-!packages/cli/test/fixtures/unit/commands/build/monorepo-detection/**/yarn.lock
-packages/cli/test/fixtures/integration
+packages/now-cli/src/util/dev/templates/*.ts
+packages/now-cli/src/util/constants.ts
+packages/now-cli/test/**/yarn.lock
+!packages/now-cli/test/dev/**/yarn.lock
+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
 __pycache__
-.vercel
-.turbo
-.eslintcache
-turbo-cache-key.json
-junit.xml

.husky/.gitignore

@@ -1 +0,0 @@
-_

.husky/pre-commit

@@ -1,4 +0,0 @@
-#!/bin/sh
-. "$(dirname "$0")/_/husky.sh"
-
-pnpm pre-commit

.kodiak.toml

@@ -1,7 +1,7 @@
 version = 1
 
 [merge]
-automerge_label = ["pr: automerge"]
+automerge_label = "automerge"
 blacklist_title_regex = "^WIP.*"
 blacklist_labels = ["work in progress"]
 method = "squash"

.node_version

@@ -1 +0,0 @@
-v16.20.2

.nowignore

@@ -0,0 +1,17 @@
+*
+
+# general
+!utils/
+!utils/run.js
+!.yarnrc
+!yarn.lock
+!package.json
+
+# api
+!api/
+!api/**
+
+# packages
+!packages/
+!packages/frameworks
+!packages/frameworks/**

.npmrc

@@ -1,6 +0,0 @@
-provenance=true
-save-exact=true
-hoist-pattern[]=!"**/@types/**"
-hoist-pattern[]=!"**/typedoc"
-hoist-pattern[]=!"**/typedoc-plugin-markdown"
-hoist-pattern[]=!"**/typedoc-plugin-mdn-links"

.nvmrc

@@ -1 +0,0 @@
-16.20.2

.prettierignore

@@ -1,35 +0,0 @@
-# https://prettier.io/docs/en/ignore.html
-
-# ignore these files with an intentional syntax error
-packages/cli/test/dev/fixtures/edge-function-error/api/edge-error-syntax.js
-packages/cli/test/fixtures/unit/commands/build/node-error/api/typescript.ts
-examples/sveltekit-1
-
-# gatsby-plugin-vercel-analytics
-packages/gatsby-plugin-vercel-analytics
-
-# ignore directories that are not source code
-node_modules
-dist
-pnpm-lock.yaml
-.changeset
-.vscode
-.DS_Store
-.next
-.vercel
-.turbo
-.eslintcache
-.output
-.vercel_build_output
-.vercel
-coverage
-turbo-cache-key.json
-/examples
-/public
-packages/*/dist
-packages/*/node_modules
-packages/**/test/fixtures
-packages/**/test/dev/fixtures
-packages/**/test/build-fixtures
-packages/**/test/cache-fixtures
-packages/cli/src/util/dev/templates/*.ts

.vercelignore

@@ -1 +0,0 @@
-packages/*/test/**

.yarnrc

@@ -0,0 +1 @@
+save-prefix ""

DEVELOPING_A_RUNTIME.md

@@ -1,34 +1,10 @@
 # Runtime Developer Reference
 
-The following page is a reference for how to create a Runtime by implementing
-the Runtime API interface. It's a way to add support for a new programming language to Vercel.
+The following page is a reference for how to create a Runtime using the available Runtime API.
 
-> Note: If you're the author of a web framework, please use the [Build Output API](https://vercel.com/docs/build-output-api/v3) instead to make your framework compatible with Vercel.
-
-A Runtime is an npm module that implements the following interface:
-
-```typescript
-interface Runtime {
-  version: number;
-  build: (options: BuildOptions) => Promise<BuildResult>;
-  prepareCache?: (options: PrepareCacheOptions) => Promise<CacheOutputs>;
-  shouldServe?: (options: ShouldServeOptions) => Promise<boolean>;
-  startDevServer?: (
-    options: StartDevServerOptions
-  ) => Promise<StartDevServerResult>;
-}
-```
-
-The `version` property and the `build()` function are the only _required_ fields.
-The rest are optional extensions that a Runtime _may_ implement in order to
-enhance functionality. These functions are documented in more detail below.
-
-Official Runtimes are published to [the npm registry](https://npmjs.com) as a package and referenced in the `use` property of the `vercel.json` configuration file.
-
-> **Note:** The `use` property in the `builds` array 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. Alternatively, the `functions` property
-> requires that you specify a specific tag published to npm, for stability purposes.
+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 `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://vercel.com/docs/runtimes) to view example usage.
 
@@ -40,160 +16,152 @@ A **required** exported constant that decides which version of the Runtime API t
 
 The latest and suggested version is `3`.
 
-**Example:**
+### `analyze`
 
-```typescript
-export const version = 3;
+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({
+  files: Files,
+  entrypoint: String,
+  workPath: String,
+  config: Object
+}) : String fingerprint
 ```
 
-### `build()`
+If you are using TypeScript, you should use the following types:
 
-A **required** exported function that returns a Serverless Function.
+```ts
+import { AnalyzeOptions } from '@now/build-utils'
 
-> What's a Serverless Function? Read about [Serverless Functions](https://vercel.com/docs/concepts/functions/serverless-functions) to learn more.
+export analyze(options: AnalyzeOptions) {
+  return 'fingerprint goes here'
+}
+```
 
-**Example:**
+### `build`
 
-```typescript
-import { BuildOptions, createLambda } from '@vercel/build-utils';
+A **required** exported function that returns a [Serverless Function](#serverless-function).
 
-export async function build(options: BuildOptions) {
-  // Build the code here…
+What's a Serverless Function? Read about [Serverless Functions](https://vercel.com/docs/v2/serverless-functions/introduction) to learn more.
+
+```js
+build({
+  files: Files,
+  entrypoint: String,
+  workPath: String,
+  config: Object,
+  meta?: {
+    isDev?: Boolean,
+    requestPath?: String,
+    filesChanged?: Array<String>,
+    filesRemoved?: Array<String>
+  }
+}) : {
+  watch?: Array<String>,
+  output: Lambda,
+  routes?: Object
+}
+```
+
+If you are using TypeScript, you should use the following types:
+
+```ts
+import { BuildOptions } from '@now/build-utils'
+
+export build(options: BuildOptions) {
+  // Build the code here
 
-  const lambda = createLambda(/* … */);
   return {
-    output: lambda,
-    routes: [
-      // If your Runtime needs to define additional routing, define it here…
-    ],
-  };
+    output: {
+      'path-to-file': File,
+      'path-to-lambda': Lambda
+    },
+    watch: [],
+    routes: {}
+  }
 }
 ```
 
-### `prepareCache()`
+### `prepareCache`
 
-An **optional** exported function that is executed after [`build()`](#build) is
-completed. The implementation should return an object of `File`s that will be
-pre-populated in the working directory for the next build run in the user's
-project. An example use-case is that `@vercel/node` uses this function to cache
-the `node_modules` directory, making it faster to install npm dependencies for
-future builds.
+An **optional** exported function that is equivalent to [`build`](#build), but it executes the instructions necessary to prepare a cache for the next run.
 
-> Note: Only files within the repo root directory can be cached.
-
-**Example:**
-
-```typescript
-import { relative } from 'path';
-import { glob, PrepareCache } from '@vercel/build-utils';
-
-export const prepareCache: PrepareCache = async ({
-  workPath,
-  repoRootPath,
-}) => {
-  // Create a mapping of file names and `File` object instances to cache here…
-  const rootDirectory = relative(repoRootPath, workPath);
-  const cache = await glob(`${rootDirectory}/some/dir/**`, repoRootPath);
-  return cache;
-};
+```js
+prepareCache({
+  files: Files,
+  entrypoint: String,
+  workPath: String,
+  cachePath: String,
+  config: Object
+}) : Files cacheOutput
 ```
 
-### `shouldServe()`
+If you are using TypeScript, you can import the types for each of these functions by using the following:
 
-An **optional** exported function that is only used by `vercel dev` in [Vercel
-CLI](https://vercel.com/download) and indicates whether a
-[Runtime](https://vercel.com/docs/runtimes) wants to be responsible for responding
-to a certain request path.
+```ts
+import { PrepareCacheOptions } from '@now/build-utils'
 
-**Example:**
-
-```typescript
-import { ShouldServeOptions } from '@vercel/build-utils';
-
-export async function shouldServe(options: ShouldServeOptions) {
-  // Determine whether or not the Runtime should respond to the request path here…
-
-  return options.requestPath === options.entrypoint;
+export prepareCache(options: PrepareCacheOptions) {
+  return { 'path-to-file': File }
 }
 ```
 
-If this function is not defined, Vercel CLI will use the [default
-implementation](https://github.com/vercel/vercel/blob/52994bfe26c5f4f179bdb49783ee57ce19334631/packages/now-build-utils/src/should-serve.ts).
+### `shouldServe`
 
-### `startDevServer()`
+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.
 
-An **optional** exported function that is only used by `vercel dev` in [Vercel
-CLI](https://vercel.com/download). If this function is defined, Vercel CLI will
-**not** invoke the `build()` function, and instead invoke this function for every
-HTTP request. It is an opportunity to provide an optimized development experience
-rather than going through the entire `build()` process that is used in production.
+```js
+shouldServe({
+  entrypoint: String,
+  files: Files,
+  config: Object,
+  requestPath: String,
+  workPath: String
+}) : Boolean
+```
 
-This function is invoked _once per HTTP request_ and is expected to spawn a child
-process which creates an HTTP server that will execute the entrypoint code when
-an HTTP request is received. This child process is _single-serve_ (only used for
-a single HTTP request). After the HTTP response is complete, `vercel dev` sends
-a shut down signal to the child process.
+If you are using TypeScript, you can import the types for each of these functions by using the following:
 
-The `startDevServer()` function returns an object with the `port` number that the
-child process' HTTP server is listening on (which should be an [ephemeral
-port](https://stackoverflow.com/a/28050404/376773)) as well as the child process'
-Process ID, which `vercel dev` uses to send the shut down signal to.
+```ts
+import { ShouldServeOptions } from '@now/build-utils'
 
-> **Hint:** To determine which ephemeral port the child process is listening on,
-> some form of [IPC](https://en.wikipedia.org/wiki/Inter-process_communication) is
-> required. For example, in `@vercel/go` the child process writes the port number
-> to [_file descriptor 3_](https://en.wikipedia.org/wiki/File_descriptor), which is read by the `startDevServer()` function
-> implementation.
-
-It may also return `null` to opt-out of this behavior for a particular request
-path or entrypoint.
-
-**Example:**
-
-```typescript
-import { spawn } from 'child_process';
-import { StartDevServerOptions } from '@vercel/build-utils';
-
-export async function startDevServer(options: StartDevServerOptions) {
-  // Create a child process which will create an HTTP server.
-  //
-  // Note: `my-runtime-dev-server` is an example dev server program name.
-  // Your implementation will spawn a different program specific to your runtime.
-  const child = spawn('my-runtime-dev-server', [options.entrypoint], {
-    stdio: ['ignore', 'inherit', 'inherit', 'pipe'],
-  });
-
-  // In this example, the child process will write the port number to FD 3…
-  const portPipe = child.stdio[3];
-  const childPort = await new Promise(resolve => {
-    portPipe.setEncoding('utf8');
-    portPipe.once('data', data => {
-      resolve(Number(data));
-    });
-  });
-
-  return { pid: child.pid, port: childPort };
+export shouldServe(options: ShouldServeOptions) {
+  return Boolean
 }
 ```
 
+If this method is not defined, Now CLI will default to [this function](https://github.com/zeit/now/blob/52994bfe26c5f4f179bdb49783ee57ce19334631/packages/now-build-utils/src/should-serve.ts).
+
+### Runtime Options
+
+The exported functions [`analyze`](#analyze), [`build`](#build), and [`prepareCache`](#preparecache) receive one argument with the following properties.
+
+**Properties:**
+
+- `files`: All source files of the project as a [Files](#files) data structure.
+- `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 `vercel.json`.
+
+## Examples
+
+Check out our [Node.js Runtime](https://github.com/zeit/now/tree/master/packages/now-node), [Go Runtime](https://github.com/zeit/now/tree/master/packages/now-go), [Python Runtime](https://github.com/zeit/now/tree/master/packages/now-python) or [Ruby Runtime](https://github.com/zeit/now/tree/master/packages/now-ruby) for examples of how to build one.
+
+## Technical Details
+
 ### Execution Context
 
-- Runtimes are executed in a Linux container that closely matches the Servereless Function runtime environment.
-- The Runtime code is executed using Node.js version **12.x**.
-- 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),
-[`prepareCache()`](#preparecache), etc.) are not guaranteed to be run in the
-same process, but the filesystem we expose (e.g.: `workPath` and the results
-of calling [`getWritableDirectory`](#getWritableDirectory) ) is retained.
+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.
 
 If you need to share state between those steps, use the filesystem.
 
 ### Directory and Cache Lifecycle
 
-When a new build is created, we pre-populate the `workPath` supplied to `analyze` with the results of the `prepareCache` step of the
-previous build.
+When a new build is created, we pre-populate the `workPath` supplied to `analyze` with the results of the `prepareCache` step of the previous build.
 
 The `analyze` step can modify that directory, and it will not be re-created when it's supplied to `build` and `prepareCache`.
 
@@ -201,87 +169,16 @@ The `analyze` step can modify that directory, and it will not be re-created when
 
 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.
 
-### Supporting Large Environment
-
-We provide the ability to support more than 4KB of environment (up to 64KB) by way of
-a Lambda runtime wrapper that is added to every Lambda function we create. These are
-supported by many of the existing Lambda runtimes, but custom runtimes may require
-additional work.
-
-The following Lambda runtime families have built-in support for the runtime wrapper:
-
-- `nodejs`
-- `python` (>= 3.8)
-- `ruby`
-- `java11`
-- `java8.al2` (not `java8`)
-- `dotnetcore`
-
-If a custom runtime is based on one of these Lambda runtimes, large environment
-support will be available without further configuration. Custom runtimes based on
-other Lambda runtimes, including those that provide the runtime via `provided` and
-`provided.al2`, must implement runtime wrapper support and indicate it via the
-`supportsWrapper` flag when calling [`createLambda`](<#createlambda()>).
-
-To add support for runtime wrappers to a custom runtime, first check the value of the
-`AWS_LAMBDA_EXEC_WRAPPER` environment variable in the bootstrap script. Its value is
-the path to the wrapper executable.
-
-The wrapper must be passed the path to the runtime as well as any parameters that the
-runtime requires. This is most easily done in a small `bootstrap` script.
-
-In this simple `bash` example, the runtime is called directly if
-`AWS_LAMBDA_EXEC_WRAPPER` has no value, otherwise the wrapper is called with the
-runtime command as parameters.
-
-```bash
-#!/bin/bash
-
-exec $AWS_LAMBDA_EXEC_WRAPPER path/to/runtime param1 param2
-```
-
-If the `bootstrap` file is not a launcher script, but the entrypoint of the runtime
-itself, replace the bootstrap process with the wrapper. Pass the path and parameters
-of the executing file, ensuring the `AWS_LAMBDA_EXEC_WRAPPER` environment variable is
-set to blank.
-
-This `bash` example uses `exec` to replace the running bootstrap process with the
-wrapper, passing its own path and parameters.
-
-```bash
-#!/bin/bash
-
-if [[ -n $AWS_LAMBDA_EXEC_WRAPPER ]]
-  __WRAPPER=$AWS_LAMBDA_EXEC_WRAPPER
-  AWS_LAMBDA_EXEC_WRAPPER=""
-  exec $__WRAPPER "$0" "${@}"
-fi
-
-# start the actual runtime functionality
-```
-
-Note that unsetting the variable may not have the desired effect due to the way
-Lambda spawns runtime processes. It is better to explicitly set it to blank.
-
-The best way to replace the existing bootstrap process is with the
-[`execve`](https://www.man7.org/linux/man-pages/man2/execve.2.html) syscall.
-This is achieved by using `exec` in `bash` to replace the running process with the wrapper,
-maintaining the same PID and environment.
-
-Once support for runtime wrappers is included, ensure `supportsWrapper` is set to
-`true` in the call to [`createLambda`](<#createlambda()>). This will inform the build
-process to enable large environment support for this runtime.
-
 ### Utilities as peerDependencies
 
-When you publish your Runtime to npm, make sure to not specify `@vercel/build-utils` (as seen below in the API definitions) as a dependency, but rather as part of `peerDependencies`.
+When you publish your Runtime to npm, make sure to not specify `@now/build-utils` (as seen below in the API definitions) as a dependency, but rather as part of `peerDependencies`.
 
-## `@vercel/build-utils` Types
+## Types
 
 ### `Files`
 
-```typescript
-import { File } from '@vercel/build-utils';
+```ts
+import { File } from '@now/build-utils';
 type Files = { [filePath: string]: File };
 ```
 
@@ -291,7 +188,7 @@ When used as an input, the `Files` object will only contain `FileRefs`. When `Fi
 
 An example of a valid output `Files` object is:
 
-```javascript
+```json
 {
   "index.html": FileRef,
   "api/index.js": Lambda
@@ -302,8 +199,8 @@ An example of a valid output `Files` object is:
 
 This is an abstract type that can be imported if you are using TypeScript.
 
-```typescript
-import { File } from '@vercel/build-utils';
+```ts
+import { File } from '@now/build-utils';
 ```
 
 Valid `File` types include:
@@ -314,104 +211,102 @@ Valid `File` types include:
 
 ### `FileRef`
 
-```typescript
-import { FileRef } from '@vercel/build-utils';
+```ts
+import { FileRef } from '@now/build-utils';
 ```
 
-This is a [class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract file instance stored in our platform, based on the file identifier string (its checksum). When a `Files` object is passed as an input to `analyze` or `build`, all its values will be instances of `FileRef`.
+This is a [JavaScript class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract file instance stored in our platform, based on the file identifier string (its checksum). When a `Files` object is passed as an input to `analyze` or `build`, all its values will be instances of `FileRef`.
 
 **Properties:**
 
-- `mode: Number` file mode
-- `digest: String` a checksum that represents the file
+- `mode : Number` file mode
+- `digest : String` a checksum that represents the file
 
 **Methods:**
 
-- `toStream(): Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
+- `toStream() : Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
 
 ### `FileFsRef`
 
-```typescript
-import { FileFsRef } from '@vercel/build-utils';
+```ts
+import { FileFsRef } from '@now/build-utils';
 ```
 
-This is a [class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract instance of a file present in the filesystem that the build process is executing in.
+This is a [JavaScript class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract instance of a file present in the filesystem that the build process is executing in.
 
 **Properties:**
 
-- `mode: Number` file mode
-- `fsPath: String` the absolute path of the file in file system
+- `mode : Number` file mode
+- `fsPath : String` the absolute path of the file in file system
 
 **Methods:**
 
-- `static async fromStream({ mode: Number, stream: Stream, fsPath: String }): FileFsRef` creates an instance of a [FileFsRef](#FileFsRef) from `Stream`, placing file at `fsPath` with `mode`
-- `toStream(): Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
+- `static async fromStream({ mode : Number, stream : Stream, fsPath : String }) : FileFsRef` creates an instance of a [FileFsRef](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object) from `Stream`, placing file at `fsPath` with `mode`
+- `toStream() : Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
 
 ### `FileBlob`
 
-```typescript
-import { FileBlob } from '@vercel/build-utils';
+```ts
+import { FileBlob } from '@now/build-utils';
 ```
 
-This is a [class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract instance of a file present in memory.
+This is a [JavaScript class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents an abstract instance of a file present in memory.
 
 **Properties:**
 
-- `mode: Number` file mode
-- `data: String | Buffer` the body of the file
+- `mode : Number` file mode
+- `data : String | Buffer` the body of the file
 
 **Methods:**
 
-- `static async fromStream({ mode: Number, stream: Stream }): FileBlob` creates an instance of a [FileBlob](#FileBlob) from [`Stream`](https://nodejs.org/api/stream.html) with `mode`
-- `toStream(): Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
+- `static async fromStream({ mode : Number, stream : Stream }) :FileBlob` creates an instance of a [FileBlob](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object) from [`Stream`](https://nodejs.org/api/stream.html) with `mode`
+- `toStream() : Stream` creates a [Stream](https://nodejs.org/api/stream.html) of the file body
 
 ### `Lambda`
 
-```typescript
-import { Lambda } from '@vercel/build-utils';
+```ts
+import { Lambda } from '@now/build-utils';
 ```
 
-This is a [class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes) that represents a Serverless Function. An instance can be created by supplying `files`, `handler`, `runtime`, and `environment` as an object to the [`createLambda`](#createlambda) helper. The instances of this class should not be created directly. Instead, invoke the [`createLambda`](#createlambda) helper function.
+This is a [JavaScript class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes), called a Serverless Function, that can be created by supplying `files`, `handler`, `runtime`, and `environment` as an object to the [`createLambda`](#createlambda) helper. The instances of this class should not be created directly. Instead, invoke the [`createLambda`](#createlambda) helper function.
 
 **Properties:**
 
-- `files: Files` the internal filesystem of the lambda
-- `handler: String` path to handler file and (optionally) a function name it exports
-- `runtime: LambdaRuntime` the name of the lambda runtime
-- `environment: Object` key-value map of handler-related (aside of those passed by user) environment variables
-- `supportsWrapper: Boolean` set to true to indicate that Lambda runtime wrappers are supported by this runtime
+- `files : Files` the internal filesystem of the lambda
+- `handler : String` path to handler file and (optionally) a function name it exports
+- `runtime : LambdaRuntime` the name of the lambda runtime
+- `environment : Object` key-value map of handler-related (aside of those passed by user) environment variables
 
 ### `LambdaRuntime`
 
 This is an abstract enumeration type that is implemented by one of the following possible `String` values:
 
-- `nodejs20.x`
-- `nodejs18.x`
-- `nodejs16.x`
+- `nodejs12.x`
+- `nodejs10.x`
+- `go1.x`
 - `java11`
-- `python3.9`
-- `dotnet6`
-- `dotnetcore3.1`
-- `ruby2.7`
-- `provided.al2`
-- `provided.al2023`
+- `python3.8`
+- `python3.6`
+- `dotnetcore2.1`
+- `ruby2.5`
+- `provided`
 
-## `@vercel/build-utils` Helper Functions
+## JavaScript API
 
-The following is exposed by `@vercel/build-utils` to simplify the process of writing Runtimes, manipulating the file system, using the above types, etc.
+The following is exposed by `@now/build-utils` to simplify the process of writing Runtimes, manipulating the file system, using the above types, etc.
 
-### `createLambda()`
+### `createLambda`
 
-Signature: `createLambda(Object spec): Lambda`
+Signature: `createLambda(Object spec) : Lambda`
 
-```typescript
-import { createLambda } from '@vercel/build-utils';
+```ts
+import { createLambda } from '@now/build-utils';
 ```
 
 Constructor for the [`Lambda`](#lambda) type.
 
 ```js
-const { createLambda, FileBlob } = require('@vercel/build-utils');
+const { createLambda, FileBlob } = require('@now/build-utils');
 await createLambda({
   runtime: 'nodejs8.10',
   handler: 'index.main',
@@ -421,34 +316,30 @@ await createLambda({
 });
 ```
 
-### `download()`
+### `download`
 
-Signature: `download(): Files`
+Signature: `download() : Files`
 
-```typescript
-import { download } from '@vercel/build-utils';
+```ts
+import { download } from '@now/build-utils';
 ```
 
-This utility allows you to download the contents of a [`Files`](#files) data
-structure, therefore creating the filesystem represented in it.
+This utility allows you to download the contents of a [`Files`](#files) data structure, therefore creating the filesystem represented in it.
 
-Since `Files` is an abstract way of representing files, you can think of
-`download()` as a way of making that virtual filesystem _real_.
+Since `Files` is an abstract way of representing files, you can think of `download` as a way of making that virtual filesystem _real_.
 
-If the **optional** `meta` property is passed (the argument for
-[`build()`](#build)), only the files that have changed are downloaded.
-This is decided using `filesRemoved` and `filesChanged` inside that object.
+If the **optional** `meta` property is passed (the argument for [build](#build)), only the files that have changed are downloaded. This is decided using `filesRemoved` and `filesChanged` inside that object.
 
 ```js
 await download(files, workPath, meta);
 ```
 
-### `glob()`
+### `glob`
 
-Signature: `glob(): Files`
+Signature: `glob() : Files`
 
-```typescript
-import { glob } from '@vercel/build-utils';
+```ts
+import { glob } from '@now/build-utils';
 ```
 
 This utility allows you to _scan_ the filesystem and return a [`Files`](#files) representation of the matched glob search string. It can be thought of as the reverse of [`download`](#download).
@@ -456,36 +347,36 @@ This utility allows you to _scan_ the filesystem and return a [`Files`](#files)
 The following trivial example downloads everything to the filesystem, only to return it back (therefore just re-creating the passed-in [`Files`](#files)):
 
 ```js
-const { glob, download } = require('@vercel/build-utils');
+const { glob, download } = require('@now/build-utils')
 
 exports.build = ({ files, workPath }) => {
-  await download(files, workPath);
-  return glob('**', workPath);
-};
+  await download(files, workPath)
+  return glob('**', workPath)
+}
 ```
 
-### `getWritableDirectory()`
+### `getWriteableDirectory`
 
-Signature: `getWritableDirectory(): String`
+Signature: `getWriteableDirectory() : String`
 
-```typescript
-import { getWritableDirectory } from '@vercel/build-utils';
+```ts
+import { getWriteableDirectory } from '@now/build-utils';
 ```
 
 In some occasions, you might want to write to a temporary directory.
 
-### `rename()`
+### `rename`
 
-Signature: `rename(Files, Function): Files`
+Signature: `rename(Files) : Files`
 
-```typescript
-import { rename } from '@vercel/build-utils';
+```ts
+import { rename } from '@now/build-utils';
 ```
 
 Renames the keys of the [`Files`](#files) object, which represent the paths. For example, to remove the `*.go` suffix you can use:
 
 ```js
-const rename = require('@vercel/build-utils')
+const rename = require('@now/build-utils')
 const originalFiles = { 'one.go': fileFsRef1, 'two.go': fileFsRef2 }
 const renamedFiles = rename(originalFiles, path => path.replace(/\.go$/, '')
 ```

LICENSE

@@ -1,202 +1,190 @@
+                             Apache License
+                       Version 2.0, January 2004
+                    https://www.apache.org/licenses/
 
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
 
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+1. Definitions.
 
-   1. Definitions.
+  "License" shall mean the terms and conditions for use, reproduction,
+  and distribution as defined by Sections 1 through 9 of this document.
 
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
+  "Licensor" shall mean the copyright owner or entity authorized by
+  the copyright owner that is granting the License.
 
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
+  "Legal Entity" shall mean the union of the acting entity and all
+  other entities that control, are controlled by, or are under common
+  control with that entity. For the purposes of this definition,
+  "control" means (i) the power, direct or indirect, to cause the
+  direction or management of such entity, whether by contract or
+  otherwise, or (ii) ownership of fifty percent (50%) or more of the
+  outstanding shares, or (iii) beneficial ownership of such entity.
 
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
+  "You" (or "Your") shall mean an individual or Legal Entity
+  exercising permissions granted by this License.
 
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
+  "Source" form shall mean the preferred form for making modifications,
+  including but not limited to software source code, documentation
+  source, and configuration files.
 
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
+  "Object" form shall mean any form resulting from mechanical
+  transformation or translation of a Source form, including but
+  not limited to compiled object code, generated documentation,
+  and conversions to other media types.
 
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
+  "Work" shall mean the work of authorship, whether in Source or
+  Object form, made available under the License, as indicated by a
+  copyright notice that is included in or attached to the work
+  (an example is provided in the Appendix below).
 
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
+  "Derivative Works" shall mean any work, whether in Source or Object
+  form, that is based on (or derived from) the Work and for which the
+  editorial revisions, annotations, elaborations, or other modifications
+  represent, as a whole, an original work of authorship. For the purposes
+  of this License, Derivative Works shall not include works that remain
+  separable from, or merely link (or bind by name) to the interfaces of,
+  the Work and Derivative Works thereof.
 
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
+  "Contribution" shall mean any work of authorship, including
+  the original version of the Work and any modifications or additions
+  to that Work or Derivative Works thereof, that is intentionally
+  submitted to Licensor for inclusion in the Work by the copyright owner
+  or by an individual or Legal Entity authorized to submit on behalf of
+  the copyright owner. For the purposes of this definition, "submitted"
+  means any form of electronic, verbal, or written communication sent
+  to the Licensor or its representatives, including but not limited to
+  communication on electronic mailing lists, source code control systems,
+  and issue tracking systems that are managed by, or on behalf of, the
+  Licensor for the purpose of discussing and improving the Work, but
+  excluding communication that is conspicuously marked or otherwise
+  designated in writing by the copyright owner as "Not a Contribution."
 
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
+  "Contributor" shall mean Licensor and any individual or Legal Entity
+  on behalf of whom a Contribution has been received by Licensor and
+  subsequently incorporated within the Work.
 
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
+2. Grant of Copyright License. Subject to the terms and conditions of
+  this License, each Contributor hereby grants to You a perpetual,
+  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+  copyright license to reproduce, prepare Derivative Works of,
+  publicly display, publicly perform, sublicense, and distribute the
+  Work and such Derivative Works in Source or Object form.
 
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
+3. Grant of Patent License. Subject to the terms and conditions of
+  this License, each Contributor hereby grants to You a perpetual,
+  worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+  (except as stated in this section) patent license to make, have made,
+  use, offer to sell, sell, import, and otherwise transfer the Work,
+  where such license applies only to those patent claims licensable
+  by such Contributor that are necessarily infringed by their
+  Contribution(s) alone or by combination of their Contribution(s)
+  with the Work to which such Contribution(s) was submitted. If You
+  institute patent litigation against any entity (including a
+  cross-claim or counterclaim in a lawsuit) alleging that the Work
+  or a Contribution incorporated within the Work constitutes direct
+  or contributory patent infringement, then any patent licenses
+  granted to You under this License for that Work shall terminate
+  as of the date such litigation is filed.
 
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
+4. Redistribution. You may reproduce and distribute copies of the
+  Work or Derivative Works thereof in any medium, with or without
+  modifications, and in Source or Object form, provided that You
+  meet the following conditions:
 
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
+  (a) You must give any other recipients of the Work or
+      Derivative Works a copy of this License; and
 
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
+  (b) You must cause any modified files to carry prominent notices
+      stating that You changed the files; and
 
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
+  (c) You must retain, in the Source form of any Derivative Works
+      that You distribute, all copyright, patent, trademark, and
+      attribution notices from the Source form of the Work,
+      excluding those notices that do not pertain to any part of
+      the Derivative Works; and
 
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
+  (d) If the Work includes a "NOTICE" text file as part of its
+      distribution, then any Derivative Works that You distribute must
+      include a readable copy of the attribution notices contained
+      within such NOTICE file, excluding those notices that do not
+      pertain to any part of the Derivative Works, in at least one
+      of the following places: within a NOTICE text file distributed
+      as part of the Derivative Works; within the Source form or
+      documentation, if provided along with the Derivative Works; or,
+      within a display generated by the Derivative Works, if and
+      wherever such third-party notices normally appear. The contents
+      of the NOTICE file are for informational purposes only and
+      do not modify the License. You may add Your own attribution
+      notices within Derivative Works that You distribute, alongside
+      or as an addendum to the NOTICE text from the Work, provided
+      that such additional attribution notices cannot be construed
+      as modifying the License.
 
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
+  You may add Your own copyright statement to Your modifications and
+  may provide additional or different license terms and conditions
+  for use, reproduction, or distribution of Your modifications, or
+  for any such Derivative Works as a whole, provided Your use,
+  reproduction, and distribution of the Work otherwise complies with
+  the conditions stated in this License.
 
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
+5. Submission of Contributions. Unless You explicitly state otherwise,
+  any Contribution intentionally submitted for inclusion in the Work
+  by You to the Licensor shall be under the terms and conditions of
+  this License, without any additional terms or conditions.
+  Notwithstanding the above, nothing herein shall supersede or modify
+  the terms of any separate license agreement you may have executed
+  with Licensor regarding such Contributions.
 
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
+6. Trademarks. This License does not grant permission to use the trade
+  names, trademarks, service marks, or product names of the Licensor,
+  except as required for reasonable and customary use in describing the
+  origin of the Work and reproducing the content of the NOTICE file.
 
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
+7. Disclaimer of Warranty. Unless required by applicable law or
+  agreed to in writing, Licensor provides the Work (and each
+  Contributor provides its Contributions) on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+  implied, including, without limitation, any warranties or conditions
+  of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+  PARTICULAR PURPOSE. You are solely responsible for determining the
+  appropriateness of using or redistributing the Work and assume any
+  risks associated with Your exercise of permissions under this License.
 
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
+8. Limitation of Liability. In no event and under no legal theory,
+  whether in tort (including negligence), contract, or otherwise,
+  unless required by applicable law (such as deliberate and grossly
+  negligent acts) or agreed to in writing, shall any Contributor be
+  liable to You for damages, including any direct, indirect, special,
+  incidental, or consequential damages of any character arising as a
+  result of this License or out of the use or inability to use the
+  Work (including but not limited to damages for loss of goodwill,
+  work stoppage, computer failure or malfunction, or any and all
+  other commercial damages or losses), even if such Contributor
+  has been advised of the possibility of such damages.
 
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
+9. Accepting Warranty or Additional Liability. While redistributing
+  the Work or Derivative Works thereof, You may choose to offer,
+  and charge a fee for, acceptance of support, warranty, indemnity,
+  or other liability obligations and/or rights consistent with this
+  License. However, in accepting such obligations, You may act only
+  on Your own behalf and on Your sole responsibility, not on behalf
+  of any other Contributor, and only if You agree to indemnify,
+  defend, and hold each Contributor harmless for any liability
+  incurred by, or claims asserted against, such Contributor by reason
+  of your accepting any such warranty or additional liability.
 
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
+END OF TERMS AND CONDITIONS
 
-   END OF TERMS AND CONDITIONS
+Copyright 2017 ZEIT, Inc.
 
-   APPENDIX: How to apply the Apache License to your work.
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
 
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
+   https://www.apache.org/licenses/LICENSE-2.0
 
-   Copyright 2017 Vercel, Inc.
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

README.md

@@ -1,44 +1,30 @@
 <p align="center">
-  <a href="https://vercel.com">
-    <img src="https://assets.vercel.com/image/upload/v1588805858/repositories/vercel/logo.png" height="96">
-    <h3 align="center">Vercel</h3>
-  </a>
+  <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>
 
-<p align="center">
-  Develop. Preview. Ship.
-</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)
 
-<p align="center">
-  <a href="https://vercel.com/docs"><strong>Documentation</strong></a> ·
-  <a href="https://vercel.com/changelog"><strong>Changelog</strong></a> ·
-  <a href="https://vercel.com/templates"><strong>Templates</strong></a> ·
-  <a href="https://vercel.com/cli"><strong>CLI</strong></a>
-</p>
-<br/>
+## Usage
 
-## Vercel
-
-Vercel’s Frontend Cloud provides the developer experience and infrastructure to build, scale, and secure a faster, more personalized Web.
-
-## Deploy
-
-Get started by [importing a project](https://vercel.com/new) or using the [Vercel CLI](https://vercel.com/cli). Then, `git push` to deploy.
+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 Vercel, check out our [documentation](https://vercel.com/docs).
 
-## Contributing
+## Caught a Bug?
 
-This project uses [pnpm](https://pnpm.io/) to install dependencies and run scripts.
+1. [Fork](https://help.github.com/articles/fork-a-repo/) this repository to your own GitHub account and then [clone](https://help.github.com/articles/cloning-a-repository/) it to your local device
+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 start using `vercel` anywhere inside the command line
 
-You can use the `dev` script to run local changes as if you were invoking Vercel CLI. For example, `vercel deploy --cwd=/path/to/project` could be run with local changes with `pnpm dev deploy --cwd=/path/to/project`.
+As always, you should use `yarn test-unit` to run the tests and see if your changes have broken anything.
 
-See the [Contributing Guidelines](./.github/CONTRIBUTING.md) for more details.
+## How to Create a Release
 
-## Reference
-
-- [Code of Conduct](./.github/CODE_OF_CONDUCT.md)
-- [Contributing Guidelines](./.github/CONTRIBUTING.md)
-- [Apache 2.0 License](./LICENSE)
+If you have write access to this repository, you can read more about how to publish a release [here](https://github.com/zeit/now/wiki/Creating-a-Release).

api/CHANGELOG.md

@@ -1,7 +0,0 @@
-# api
-
-## 0.0.1
-
-### Patch Changes
-
-- fix RSC matching behavior & 404 status code on `fallback: false` ([#10388](https://github.com/vercel/vercel/pull/10388))

api/_lib/examples/github-repo-info.ts

@@ -51,11 +51,7 @@ export async function getGitHubRepoInfo(repo: Repo) {
     data.subdir = repo.path.slice(subdirPath.length).split('/');
   }
 
-  if (
-    data.id === 'vercel/vercel' &&
-    data.subdir &&
-    data.subdir[0] === 'examples'
-  ) {
+  if (data.id === 'zeit/now' && data.subdir && data.subdir[0] === 'examples') {
     // from our examples, add `homepage` and `description` fields
     const example = data.subdir[1];
     const exampleList = await getExampleList();

api/_lib/examples/summary.ts

@@ -2,19 +2,19 @@
  * Get example list from extracted folder
  */
 
+import { join } from 'path';
 import { lstatSync, existsSync, readdirSync } from 'fs';
 
 const exists = (path: string) => existsSync(path);
 const isDotFile = (name: string) => name.startsWith('.');
 const isDirectory = (path: string) => lstatSync(path).isDirectory();
 
-export function summary(source: string): string[] {
+export function summary(source: string) {
   if (!exists(source) || !isDirectory(source)) {
     return [];
   }
 
-  return readdirSync(source, { withFileTypes: true })
-    .filter(d => !isDotFile(d.name))
-    .filter(d => d.isDirectory())
-    .map(d => d.name);
+  return readdirSync(source)
+    .filter(name => !isDotFile(name))
+    .filter(name => isDirectory(join(source, name)));
 }

api/_lib/script/build.ts

@@ -1,93 +0,0 @@
-import fs from 'fs/promises';
-import { join, dirname } from 'path';
-import { getExampleList } from '../examples/example-list';
-import { mapOldToNew } from '../examples/map-old-to-new';
-
-const repoRoot = join(__dirname, '..', '..', '..');
-const pubDir = join(repoRoot, 'public');
-
-async function main() {
-  console.log(`Building static frontend ${repoRoot}...`);
-
-  await fs.rm(pubDir, { recursive: true, force: true });
-  await fs.mkdir(pubDir);
-
-  await fs.cp(
-    join(repoRoot, 'packages', 'frameworks', 'logos'),
-    join(pubDir, 'framework-logos'),
-    { recursive: true, force: true }
-  );
-
-  await fs.cp(
-    join(repoRoot, 'packages', 'fs-detectors', 'logos'),
-    join(pubDir, 'monorepo-logos'),
-    { recursive: true, force: true }
-  );
-
-  const examples = await getExampleList();
-  const pathListAll = join(pubDir, 'list-all.json');
-  await fs.writeFile(pathListAll, JSON.stringify(examples));
-
-  const exampleDirs = await fs.readdir(join(repoRoot, 'examples'), {
-    withFileTypes: true,
-  });
-
-  const existingExamples = exampleDirs
-    .filter(
-      dir =>
-        dir.isDirectory() &&
-        dir.name !== 'node_modules' &&
-        dir.name !== '__tests__'
-    )
-    .map(dir => ({
-      name: dir.name,
-      visible: true,
-      suggestions: [],
-    }));
-
-  const oldExamples = Object.keys(mapOldToNew).map(key => ({
-    name: key,
-    visible: false,
-    suggestions: mapOldToNew[key],
-  }));
-
-  const pathList = join(pubDir, 'list.json');
-  await fs.writeFile(
-    pathList,
-    JSON.stringify([...existingExamples, ...oldExamples])
-  );
-
-  const tarballsDir = join(pubDir, 'tarballs');
-  const packagesDir = join(repoRoot, 'packages');
-  const packages = await fs.readdir(packagesDir);
-  for (const pkg of packages) {
-    const fullDir = join(packagesDir, pkg);
-    const packageJsonRaw = await fs.readFile(
-      join(fullDir, 'package.json'),
-      'utf-8'
-    );
-    const packageJson = JSON.parse(packageJsonRaw);
-    const files = await fs.readdir(fullDir);
-    const tarballName = files.find(f => /^vercel-.+\.tgz$/.test(f));
-    if (!tarballName) {
-      throw new Error(
-        `Expected vercel-*.tgz in ${fullDir} but found ${JSON.stringify(
-          files,
-          null,
-          2
-        )}`
-      );
-    }
-    const srcTarballPath = join(fullDir, tarballName);
-    const destTarballPath = join(tarballsDir, `${packageJson.name}.tgz`);
-    await fs.mkdir(dirname(destTarballPath), { recursive: true });
-    await fs.copyFile(srcTarballPath, destTarballPath);
-  }
-
-  console.log('Completed building static frontend.');
-}
-
-main().catch(err => {
-  console.log('error running build:', err);
-  process.exit(1);
-});

api/_lib/util/error-handler.ts

@@ -13,8 +13,6 @@ function initSentry() {
   sentryInitDone = true;
 
   init({
-    // Cannot figure out whats going wrong here. VSCode resolves this fine. But when we build it blows up.
-    // @ts-ignore
     dsn: assertEnv('SENTRY_DSN'),
     environment: process.env.NODE_ENV || 'production',
     release: `${serviceName}`,

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

@@ -1,10 +1,10 @@
-import { VercelRequest, VercelResponse } from '@vercel/node';
+import { NowRequest, NowResponse } from '@now/node';
 import { errorHandler } from './error-handler';
 
-type Handler = (req: VercelRequest, res: VercelResponse) => Promise<any>;
+type Handler = (req: NowRequest, res: NowResponse) => Promise<any>;
 
 export function withApiHandler(handler: Handler): Handler {
-  return async (req: VercelRequest, res: VercelResponse) => {
+  return async (req: NowRequest, res: NowResponse) => {
     res.setHeader('Access-Control-Allow-Origin', '*');
     res.setHeader('Access-Control-Allow-Methods', 'GET');
     res.setHeader(

api/examples/download/[segment].ts

@@ -2,7 +2,7 @@ import fs from 'fs';
 // @ts-ignore
 import tar from 'tar-fs';
 import { extract } from '../../_lib/examples/extract';
-import { VercelRequest, VercelResponse } from '@vercel/node';
+import { NowRequest, NowResponse } from '@now/node';
 import { withApiHandler } from '../../_lib/util/with-api-handler';
 
 const TMP_DIR = '/tmp';
@@ -11,12 +11,12 @@ function isDirectory(path: string) {
   return fs.existsSync(path) && fs.lstatSync(path).isDirectory();
 }
 
-function notFound(res: VercelResponse, message: string) {
+function notFound(res: NowResponse, message: string) {
   return res.status(404).send({
     error: {
       code: 'not_found',
-      message,
-    },
+      message
+    }
   });
 }
 
@@ -35,10 +35,7 @@ function streamToBuffer(stream: any) {
   });
 }
 
-export default withApiHandler(async function (
-  req: VercelRequest,
-  res: VercelResponse
-) {
+export default withApiHandler(async function(req: NowRequest, res: NowResponse) {
   const ext = '.tar.gz';
   const { segment = '' } = req.query;
 
@@ -48,8 +45,8 @@ export default withApiHandler(async function (
 
   const example = segment.slice(0, -ext.length);
 
-  await extract('https://github.com/vercel/vercel/archive/main.zip', TMP_DIR);
-  const directory = `${TMP_DIR}/vercel-main/examples/${example}`;
+  await extract('https://github.com/zeit/now/archive/master.zip', TMP_DIR);
+  const directory = `${TMP_DIR}/now-master/examples/${example}`;
 
   if (!isDirectory(directory)) {
     return notFound(res, `Example '${example}' was not found.`);

api/examples/info.ts

@@ -1,16 +1,16 @@
 // A proxy to get the basic info of an existing github/gitlab repo:
-// GET /info?repo=vercel/micro
+// GET /info?repo=zeit/micro
 
 // @ts-ignore
 import parseGitUrl from 'parse-github-url';
-import { VercelRequest, VercelResponse } from '@vercel/node';
+import { NowRequest, NowResponse } from '@now/node';
 import { withApiHandler } from '../_lib/util/with-api-handler';
 import { getGitHubRepoInfo } from '../_lib/examples/github-repo-info';
 import { getGitLabRepoInfo } from '../_lib/examples/gitlab-repo-info';
 
-export default withApiHandler(async function (
-  req: VercelRequest,
-  res: VercelResponse
+export default withApiHandler(async function(
+  req: NowRequest,
+  res: NowResponse
 ) {
   const repoPath = decodeURIComponent((req.query.repo as string) || '');
 

api/examples/list-all.ts

@@ -0,0 +1,10 @@
+import { NowRequest, NowResponse } from '@now/node';
+import { getExampleList } from '../_lib/examples/example-list';
+import { withApiHandler } from '../_lib/util/with-api-handler';
+
+export default withApiHandler(async function(
+  req: NowRequest,
+  res: NowResponse
+) {
+  res.status(200).json(await getExampleList());
+});

api/examples/list.ts

@@ -0,0 +1,27 @@
+import { extract } from '../_lib/examples/extract';
+import { summary } from '../_lib/examples/summary';
+import { NowRequest, NowResponse } from '@now/node';
+import { mapOldToNew } from '../_lib/examples/map-old-to-new';
+import { withApiHandler } from '../_lib/util/with-api-handler';
+
+export default withApiHandler(async function(
+  req: NowRequest,
+  res: NowResponse
+) {
+  await extract('https://github.com/zeit/now/archive/master.zip', '/tmp');
+  const exampleList = summary('/tmp/now-master/examples');
+
+  const existingExamples = Array.from(exampleList).map(key => ({
+    name: key,
+    visible: true,
+    suggestions: [],
+  }));
+
+  const oldExamples = Object.keys(mapOldToNew).map(key => ({
+    name: key,
+    visible: false,
+    suggestions: mapOldToNew[key],
+  }));
+
+  res.status(200).json([...existingExamples, ...oldExamples]);
+});

api/frameworks.ts

@@ -1,27 +1,23 @@
-import { VercelRequest, VercelResponse } from '@vercel/node';
+import { NowRequest, NowResponse } from '@now/node';
 import { withApiHandler } from './_lib/util/with-api-handler';
-import _frameworks, { Framework } from '../packages/frameworks';
+import frameworkList, { Framework } from '../packages/frameworks';
 
-const frameworks = (_frameworks as Framework[])
-  .sort(
-    (a, b) =>
-      (a.sort || Number.MAX_SAFE_INTEGER) - (b.sort || Number.MAX_SAFE_INTEGER)
-  )
-  .map(frameworkItem => {
-    const framework = {
-      ...frameworkItem,
-      detectors: undefined,
-      sort: undefined,
-      dependency: undefined,
-      defaultRoutes: undefined,
-    };
+const frameworks = (frameworkList as Framework[]).map(frameworkItem => {
+  const framework = {
+    ...frameworkItem,
+    detectors: undefined,
+  };
 
-    return framework;
-  });
+  if (framework.logo) {
+    framework.logo = `https://res.cloudinary.com/zeit-inc/image/fetch/${framework.logo}`;
+  }
 
-export default withApiHandler(async function (
-  req: VercelRequest,
-  res: VercelResponse
+  return framework;
+});
+
+export default withApiHandler(async function(
+  req: NowRequest,
+  res: NowResponse
 ) {
   res.setHeader('Access-Control-Allow-Origin', '*');
   res.setHeader('Access-Control-Allow-Methods', 'GET');

api/package.json

@@ -1,21 +1,24 @@
 {
   "name": "api",
   "private": true,
-  "version": "0.0.1",
-  "description": "API for the vercel/vercel repo",
+  "version": "0.0.0",
+  "description": "API for the zeit/now repo",
   "main": "index.js",
-  "scripts": {},
+  "scripts": {
+    "build": "yarn --cwd .. && node ../utils/run.js build all"
+  },
   "dependencies": {
     "@sentry/node": "5.11.1",
     "got": "10.2.1",
-    "node-fetch": "2.6.7",
+    "node-fetch": "2.6.0",
     "parse-github-url": "1.0.2",
     "tar-fs": "2.0.0",
+    "typescript": "3.7.4",
     "unzip-stream": "0.3.0"
   },
   "devDependencies": {
-    "@types/node": "16.18.11",
-    "@types/node-fetch": "2.5.4",
-    "@vercel/node": "*"
+    "@now/node": "1.3.3",
+    "@types/node": "13.1.4",
+    "@types/node-fetch": "2.5.4"
   }
 }

api/tsconfig.json

@@ -1,16 +1,15 @@
 {
   "compilerOptions": {
-    "target": "ES2021",
+    "target": "esnext",
     "skipLibCheck": true,
     "strict": false,
     "forceConsistentCasingInFileNames": true,
     "noEmit": true,
-    "noEmitOnError": true,
     "esModuleInterop": true,
     "module": "commonjs",
     "moduleResolution": "node",
     "resolveJsonModule": true,
     "isolatedModules": true
   },
-  "include": ["examples", "frameworks.ts", "_lib"]
+  "include": ["examples", "frameworks.ts"]
 }

api/yarn.lock

@@ -0,0 +1,468 @@
+# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
+# yarn lockfile v1
+
+
+"@now/node@1.3.3":
+  version "1.3.3"
+  resolved "https://registry.yarnpkg.com/@now/node/-/node-1.3.3.tgz#5407cb6a730d4dd9b6b6b0bc4a316f29086c9feb"
+  integrity sha512-s1qajtQttWhhSs1k6FX0/6eTFYFUplzultrQeKfOPMoYzzz6OxDq5qrQ3elpsGlZlDVmO+x+JOJ7yad+3yBgpg==
+  dependencies:
+    "@types/node" "*"
+
+"@sentry/apm@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/apm/-/apm-5.11.1.tgz#cc89fa4150056fbf009f92eca94fccc3980db34e"
+  integrity sha512-4iZH11p/7w9IMLT9hqNY1+EqLESltiIoF6/YsbpK93sXWGEs8VQ83IuvGuKWxajvHgDmj4ND0TxIliTsYqTqFw==
+  dependencies:
+    "@sentry/browser" "5.11.1"
+    "@sentry/hub" "5.11.1"
+    "@sentry/minimal" "5.11.1"
+    "@sentry/types" "5.11.0"
+    "@sentry/utils" "5.11.1"
+    tslib "^1.9.3"
+
+"@sentry/browser@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/browser/-/browser-5.11.1.tgz#337ffcb52711b23064c847a07629e966f54a5ebb"
+  integrity sha512-oqOX/otmuP92DEGRyZeBuQokXdeT9HQRxH73oqIURXXNLMP3PWJALSb4HtT4AftEt/2ROGobZLuA4TaID6My/Q==
+  dependencies:
+    "@sentry/core" "5.11.1"
+    "@sentry/types" "5.11.0"
+    "@sentry/utils" "5.11.1"
+    tslib "^1.9.3"
+
+"@sentry/core@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/core/-/core-5.11.1.tgz#9e2da485e196ae32971545c1c49ee6fe719930e2"
+  integrity sha512-BpvPosVNT20Xso4gAV54Lu3KqDmD20vO63HYwbNdST5LUi8oYV4JhvOkoBraPEM2cbBwQvwVcFdeEYKk4tin9A==
+  dependencies:
+    "@sentry/hub" "5.11.1"
+    "@sentry/minimal" "5.11.1"
+    "@sentry/types" "5.11.0"
+    "@sentry/utils" "5.11.1"
+    tslib "^1.9.3"
+
+"@sentry/hub@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/hub/-/hub-5.11.1.tgz#ddcb865563fae53852d405885c46b4c6de68a91b"
+  integrity sha512-ucKprYCbGGLLjVz4hWUqHN9KH0WKUkGf5ZYfD8LUhksuobRkYVyig0ZGbshECZxW5jcDTzip4Q9Qimq/PkkXBg==
+  dependencies:
+    "@sentry/types" "5.11.0"
+    "@sentry/utils" "5.11.1"
+    tslib "^1.9.3"
+
+"@sentry/minimal@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/minimal/-/minimal-5.11.1.tgz#0e705d01a567282d8fbbda2aed848b4974cc3cec"
+  integrity sha512-HK8zs7Pgdq7DsbZQTThrhQPrJsVWzz7MaluAbQA0rTIAJ3TvHKQpsVRu17xDpjZXypqWcKCRsthDrC4LxDM1Bg==
+  dependencies:
+    "@sentry/hub" "5.11.1"
+    "@sentry/types" "5.11.0"
+    tslib "^1.9.3"
+
+"@sentry/node@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/node/-/node-5.11.1.tgz#2a9c18cd1209cfdf7a69b9d91303413149d2c910"
+  integrity sha512-FbJs0blJ36gEzE0rc2yBfA/KE+kXOLl8MUfFTcyJCBdCGF8XMETDCmgINnJ4TyBUJviwKoPw2TCk9TL2pa/A1w==
+  dependencies:
+    "@sentry/apm" "5.11.1"
+    "@sentry/core" "5.11.1"
+    "@sentry/hub" "5.11.1"
+    "@sentry/types" "5.11.0"
+    "@sentry/utils" "5.11.1"
+    cookie "^0.3.1"
+    https-proxy-agent "^4.0.0"
+    lru_map "^0.3.3"
+    tslib "^1.9.3"
+
+"@sentry/types@5.11.0":
+  version "5.11.0"
+  resolved "https://registry.yarnpkg.com/@sentry/types/-/types-5.11.0.tgz#40f0f3174362928e033ddd9725d55e7c5cb7c5b6"
+  integrity sha512-1Uhycpmeo1ZK2GLvrtwZhTwIodJHcyIS6bn+t4IMkN9MFoo6ktbAfhvexBDW/IDtdLlCGJbfm8nIZerxy0QUpg==
+
+"@sentry/utils@5.11.1":
+  version "5.11.1"
+  resolved "https://registry.yarnpkg.com/@sentry/utils/-/utils-5.11.1.tgz#aa19fcc234cf632257b2281261651d2fac967607"
+  integrity sha512-O0Zl4R2JJh8cTkQ8ZL2cDqGCmQdpA5VeXpuBbEl1v78LQPkBDISi35wH4mKmLwMsLBtTVpx2UeUHBj0KO5aLlA==
+  dependencies:
+    "@sentry/types" "5.11.0"
+    tslib "^1.9.3"
+
+"@sindresorhus/is@^1.0.0":
+  version "1.2.0"
+  resolved "https://registry.yarnpkg.com/@sindresorhus/is/-/is-1.2.0.tgz#63ce3638cb85231f3704164c90a18ef816da3fb7"
+  integrity sha512-mwhXGkRV5dlvQc4EgPDxDxO6WuMBVymGFd1CA+2Y+z5dG9MNspoQ+AWjl/Ld1MnpCL8AKbosZlDVohqcIwuWsw==
+
+"@szmarczak/http-timer@^4.0.0":
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/@szmarczak/http-timer/-/http-timer-4.0.0.tgz#309789ccb7842ff1e41848cf43da587f78068836"
+  integrity sha512-3yoXv8OtGr/r3R5gaWWNQ3VUoQ5G3Gmo8DXX95V14ZVvE2b7Pj6Ide9uIDON8ym4D/ItyfL9ejohYUPqOyvRXw==
+  dependencies:
+    defer-to-connect "^1.1.1"
+
+"@types/cacheable-request@^6.0.1":
+  version "6.0.1"
+  resolved "https://registry.yarnpkg.com/@types/cacheable-request/-/cacheable-request-6.0.1.tgz#5d22f3dded1fd3a84c0bbeb5039a7419c2c91976"
+  integrity sha512-ykFq2zmBGOCbpIXtoVbz4SKY5QriWPh3AjyU4G74RYbtt5yOc5OfaY75ftjg7mikMOla1CTGpX3lLbuJh8DTrQ==
+  dependencies:
+    "@types/http-cache-semantics" "*"
+    "@types/keyv" "*"
+    "@types/node" "*"
+    "@types/responselike" "*"
+
+"@types/http-cache-semantics@*":
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/@types/http-cache-semantics/-/http-cache-semantics-4.0.0.tgz#9140779736aa2655635ee756e2467d787cfe8a2a"
+  integrity sha512-c3Xy026kOF7QOTn00hbIllV1dLR9hG9NkSrLQgCVs8NF6sBU+VGWjD3wLPhmh1TYAc7ugCFsvHYMN4VcBN1U1A==
+
+"@types/keyv@*":
+  version "3.1.1"
+  resolved "https://registry.yarnpkg.com/@types/keyv/-/keyv-3.1.1.tgz#e45a45324fca9dab716ab1230ee249c9fb52cfa7"
+  integrity sha512-MPtoySlAZQ37VoLaPcTHCu1RWJ4llDkULYZIzOYxlhxBqYPB0RsRlmMU0R6tahtFe27mIdkHV+551ZWV4PLmVw==
+  dependencies:
+    "@types/node" "*"
+
+"@types/node-fetch@2.5.4":
+  version "2.5.4"
+  resolved "https://registry.yarnpkg.com/@types/node-fetch/-/node-fetch-2.5.4.tgz#5245b6d8841fc3a6208b82291119bc11c4e0ce44"
+  integrity sha512-Oz6id++2qAOFuOlE1j0ouk1dzl3mmI1+qINPNBhi9nt/gVOz0G+13Ao6qjhdF0Ys+eOkhu6JnFmt38bR3H0POQ==
+  dependencies:
+    "@types/node" "*"
+
+"@types/node@*", "@types/node@13.1.4":
+  version "13.1.4"
+  resolved "https://registry.yarnpkg.com/@types/node/-/node-13.1.4.tgz#4cfd90175a200ee9b02bd6b1cd19bc349741607e"
+  integrity sha512-Lue/mlp2egZJoHXZr4LndxDAd7i/7SQYhV0EjWfb/a4/OZ6tuVwMCVPiwkU5nsEipxEf7hmkSU7Em5VQ8P5NGA==
+
+"@types/responselike@*":
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/@types/responselike/-/responselike-1.0.0.tgz#251f4fe7d154d2bad125abe1b429b23afd262e29"
+  integrity sha512-85Y2BjiufFzaMIlvJDvTTB8Fxl2xfLo4HgmHzVBz08w4wDePCTjYw66PdrolO0kzli3yam/YCgRufyo1DdQVTA==
+  dependencies:
+    "@types/node" "*"
+
+agent-base@5:
+  version "5.1.1"
+  resolved "https://registry.yarnpkg.com/agent-base/-/agent-base-5.1.1.tgz#e8fb3f242959db44d63be665db7a8e739537a32c"
+  integrity sha512-TMeqbNl2fMW0nMjTEPOwe3J/PRFP4vqeoNuQMG0HlMrtm5QxKqdvAkZ1pRBQ/ulIyDD5Yq0nJ7YbdD8ey0TO3g==
+
+binary@^0.3.0:
+  version "0.3.0"
+  resolved "https://registry.yarnpkg.com/binary/-/binary-0.3.0.tgz#9f60553bc5ce8c3386f3b553cff47462adecaa79"
+  integrity sha1-n2BVO8XOjDOG87VTz/R0Yq3sqnk=
+  dependencies:
+    buffers "~0.1.1"
+    chainsaw "~0.1.0"
+
+bl@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/bl/-/bl-3.0.0.tgz#3611ec00579fd18561754360b21e9f784500ff88"
+  integrity sha512-EUAyP5UHU5hxF8BPT0LKW8gjYLhq1DQIcneOX/pL/m2Alo+OYDQAJlHq+yseMP50Os2nHXOSic6Ss3vSQeyf4A==
+  dependencies:
+    readable-stream "^3.0.1"
+
+buffers@~0.1.1:
+  version "0.1.1"
+  resolved "https://registry.yarnpkg.com/buffers/-/buffers-0.1.1.tgz#b24579c3bed4d6d396aeee6d9a8ae7f5482ab7bb"
+  integrity sha1-skV5w77U1tOWru5tmorn9Ugqt7s=
+
+cacheable-lookup@^0.2.1:
+  version "0.2.1"
+  resolved "https://registry.yarnpkg.com/cacheable-lookup/-/cacheable-lookup-0.2.1.tgz#f474ae2c686667d7ea08c43409ad31b2b31b26c2"
+  integrity sha512-BQ8MRjxJASEq2q+w0SusPU3B054gS278K8sj58QCLMZIso5qG05+MdCdmXxuyVlfvI8h4bPsNOavVUauVCGxrg==
+  dependencies:
+    keyv "^3.1.0"
+
+cacheable-request@^7.0.0:
+  version "7.0.0"
+  resolved "https://registry.yarnpkg.com/cacheable-request/-/cacheable-request-7.0.0.tgz#12421aa084e943ec81eac8c93e56af90c624788a"
+  integrity sha512-UVG4gMn3WjnAeFBBx7RFoprgOANIAkMwN5Dta6ONmfSwrCxfm0Ip7g0mIBxIRJZX9aDsoID0Ry3dU5Pr0csKKA==
+  dependencies:
+    clone-response "^1.0.2"
+    get-stream "^5.1.0"
+    http-cache-semantics "^4.0.0"
+    keyv "^3.0.0"
+    lowercase-keys "^2.0.0"
+    normalize-url "^4.1.0"
+    responselike "^2.0.0"
+
+chainsaw@~0.1.0:
+  version "0.1.0"
+  resolved "https://registry.yarnpkg.com/chainsaw/-/chainsaw-0.1.0.tgz#5eab50b28afe58074d0d58291388828b5e5fbc98"
+  integrity sha1-XqtQsor+WAdNDVgpE4iCi15fvJg=
+  dependencies:
+    traverse ">=0.3.0 <0.4"
+
+chownr@^1.1.1:
+  version "1.1.3"
+  resolved "https://registry.yarnpkg.com/chownr/-/chownr-1.1.3.tgz#42d837d5239688d55f303003a508230fa6727142"
+  integrity sha512-i70fVHhmV3DtTl6nqvZOnIjbY0Pe4kAUjwHj8z0zAdgBtYrJyYwLKCCuRBQ5ppkyL0AkN7HKRnETdmdp1zqNXw==
+
+clone-response@^1.0.2:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/clone-response/-/clone-response-1.0.2.tgz#d1dc973920314df67fbeb94223b4ee350239e96b"
+  integrity sha1-0dyXOSAxTfZ/vrlCI7TuNQI56Ws=
+  dependencies:
+    mimic-response "^1.0.0"
+
+cookie@^0.3.1:
+  version "0.3.1"
+  resolved "https://registry.yarnpkg.com/cookie/-/cookie-0.3.1.tgz#e7e0a1f9ef43b4c8ba925c5c5a96e806d16873bb"
+  integrity sha1-5+Ch+e9DtMi6klxcWpboBtFoc7s=
+
+debug@4:
+  version "4.1.1"
+  resolved "https://registry.yarnpkg.com/debug/-/debug-4.1.1.tgz#3b72260255109c6b589cee050f1d516139664791"
+  integrity sha512-pYAIzeRo8J6KPEaJ0VWOh5Pzkbw/RetuzehGM7QRRX5he4fPHx2rdKMB256ehJCkX+XRQm16eZLqLNS8RSZXZw==
+  dependencies:
+    ms "^2.1.1"
+
+decompress-response@^5.0.0:
+  version "5.0.0"
+  resolved "https://registry.yarnpkg.com/decompress-response/-/decompress-response-5.0.0.tgz#7849396e80e3d1eba8cb2f75ef4930f76461cb0f"
+  integrity sha512-TLZWWybuxWgoW7Lykv+gq9xvzOsUjQ9tF09Tj6NSTYGMTCHNXzrPnD6Hi+TgZq19PyTAGH4Ll/NIM/eTGglnMw==
+  dependencies:
+    mimic-response "^2.0.0"
+
+defer-to-connect@^1.1.1:
+  version "1.1.1"
+  resolved "https://registry.yarnpkg.com/defer-to-connect/-/defer-to-connect-1.1.1.tgz#88ae694b93f67b81815a2c8c769aef6574ac8f2f"
+  integrity sha512-J7thop4u3mRTkYRQ+Vpfwy2G5Ehoy82I14+14W4YMDLKdWloI9gSzRbV30s/NckQGVJtPkWNcW4oMAUigTdqiQ==
+
+duplexer3@^0.1.4:
+  version "0.1.4"
+  resolved "https://registry.yarnpkg.com/duplexer3/-/duplexer3-0.1.4.tgz#ee01dd1cac0ed3cbc7fdbea37dc0a8f1ce002ce2"
+  integrity sha1-7gHdHKwO08vH/b6jfcCo8c4ALOI=
+
+end-of-stream@^1.1.0, end-of-stream@^1.4.1:
+  version "1.4.4"
+  resolved "https://registry.yarnpkg.com/end-of-stream/-/end-of-stream-1.4.4.tgz#5ae64a5f45057baf3626ec14da0ca5e4b2431eb0"
+  integrity sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==
+  dependencies:
+    once "^1.4.0"
+
+fs-constants@^1.0.0:
+  version "1.0.0"
+  resolved "https://registry.yarnpkg.com/fs-constants/-/fs-constants-1.0.0.tgz#6be0de9be998ce16af8afc24497b9ee9b7ccd9ad"
+  integrity sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==
+
+get-stream@^5.0.0, get-stream@^5.1.0:
+  version "5.1.0"
+  resolved "https://registry.yarnpkg.com/get-stream/-/get-stream-5.1.0.tgz#01203cdc92597f9b909067c3e656cc1f4d3c4dc9"
+  integrity sha512-EXr1FOzrzTfGeL0gQdeFEvOMm2mzMOglyiOXSTpPC+iAjAKftbr3jpCMWynogwYnM+eSj9sHGc6wjIcDvYiygw==
+  dependencies:
+    pump "^3.0.0"
+
+got@10.2.1:
+  version "10.2.1"
+  resolved "https://registry.yarnpkg.com/got/-/got-10.2.1.tgz#7087485482fb31aa6e6399fd493dd04639da117b"
+  integrity sha512-IQX//hGm5oLjUj743GJG30U2RzjS58ZlhQQjwQXjsyR50TTD+etVMHlMEbNxYJGWVFa0ASgDVhRkAvQPe6M9iQ==
+  dependencies:
+    "@sindresorhus/is" "^1.0.0"
+    "@szmarczak/http-timer" "^4.0.0"
+    "@types/cacheable-request" "^6.0.1"
+    cacheable-lookup "^0.2.1"
+    cacheable-request "^7.0.0"
+    decompress-response "^5.0.0"
+    duplexer3 "^0.1.4"
+    get-stream "^5.0.0"
+    lowercase-keys "^2.0.0"
+    mimic-response "^2.0.0"
+    p-cancelable "^2.0.0"
+    responselike "^2.0.0"
+    to-readable-stream "^2.0.0"
+    type-fest "^0.8.0"
+
+http-cache-semantics@^4.0.0:
+  version "4.0.3"
+  resolved "https://registry.yarnpkg.com/http-cache-semantics/-/http-cache-semantics-4.0.3.tgz#495704773277eeef6e43f9ab2c2c7d259dda25c5"
+  integrity sha512-TcIMG3qeVLgDr1TEd2XvHaTnMPwYQUQMIBLy+5pLSDKYFc7UIqj39w8EGzZkaxoLv/l2K8HaI0t5AVA+YYgUew==
+
+https-proxy-agent@^4.0.0:
+  version "4.0.0"
+  resolved "https://registry.yarnpkg.com/https-proxy-agent/-/https-proxy-agent-4.0.0.tgz#702b71fb5520a132a66de1f67541d9e62154d82b"
+  integrity sha512-zoDhWrkR3of1l9QAL8/scJZyLu8j/gBkcwcaQOZh7Gyh/+uJQzGVETdgT30akuwkpL8HTRfssqI3BZuV18teDg==
+  dependencies:
+    agent-base "5"
+    debug "4"
+
+inherits@^2.0.3:
+  version "2.0.4"
+  resolved "https://registry.yarnpkg.com/inherits/-/inherits-2.0.4.tgz#0fa2c64f932917c3433a0ded55363aae37416b7c"
+  integrity sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==
+
+json-buffer@3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/json-buffer/-/json-buffer-3.0.0.tgz#5b1f397afc75d677bde8bcfc0e47e1f9a3d9a898"
+  integrity sha1-Wx85evx11ne96Lz8Dkfh+aPZqJg=
+
+keyv@^3.0.0, keyv@^3.1.0:
+  version "3.1.0"
+  resolved "https://registry.yarnpkg.com/keyv/-/keyv-3.1.0.tgz#ecc228486f69991e49e9476485a5be1e8fc5c4d9"
+  integrity sha512-9ykJ/46SN/9KPM/sichzQ7OvXyGDYKGTaDlKMGCAlg2UK8KRy4jb0d8sFc+0Tt0YYnThq8X2RZgCg74RPxgcVA==
+  dependencies:
+    json-buffer "3.0.0"
+
+lowercase-keys@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/lowercase-keys/-/lowercase-keys-2.0.0.tgz#2603e78b7b4b0006cbca2fbcc8a3202558ac9479"
+  integrity sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA==
+
+lru_map@^0.3.3:
+  version "0.3.3"
+  resolved "https://registry.yarnpkg.com/lru_map/-/lru_map-0.3.3.tgz#b5c8351b9464cbd750335a79650a0ec0e56118dd"
+  integrity sha1-tcg1G5Rky9dQM1p5ZQoOwOVhGN0=
+
+mimic-response@^1.0.0:
+  version "1.0.1"
+  resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-1.0.1.tgz#4923538878eef42063cb8a3e3b0798781487ab1b"
+  integrity sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==
+
+mimic-response@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/mimic-response/-/mimic-response-2.0.0.tgz#996a51c60adf12cb8a87d7fb8ef24c2f3d5ebb46"
+  integrity sha512-8ilDoEapqA4uQ3TwS0jakGONKXVJqpy+RpM+3b7pLdOjghCrEiGp9SRkFbUHAmZW9vdnrENWHjaweIoTIJExSQ==
+
+minimist@0.0.8:
+  version "0.0.8"
+  resolved "https://registry.yarnpkg.com/minimist/-/minimist-0.0.8.tgz#857fcabfc3397d2625b8228262e86aa7a011b05d"
+  integrity sha1-hX/Kv8M5fSYluCKCYuhqp6ARsF0=
+
+mkdirp@^0.5.1:
+  version "0.5.1"
+  resolved "https://registry.yarnpkg.com/mkdirp/-/mkdirp-0.5.1.tgz#30057438eac6cf7f8c4767f38648d6697d75c903"
+  integrity sha1-MAV0OOrGz3+MR2fzhkjWaX11yQM=
+  dependencies:
+    minimist "0.0.8"
+
+ms@^2.1.1:
+  version "2.1.2"
+  resolved "https://registry.yarnpkg.com/ms/-/ms-2.1.2.tgz#d09d1f357b443f493382a8eb3ccd183872ae6009"
+  integrity sha512-sGkPx+VjMtmA6MX27oA4FBFELFCZZ4S4XqeGOXCv68tT+jb3vk/RyaKWP0PTKyWtmLSM0b+adUTEvbs1PEaH2w==
+
+node-fetch@2.6.0:
+  version "2.6.0"
+  resolved "https://registry.yarnpkg.com/node-fetch/-/node-fetch-2.6.0.tgz#e633456386d4aa55863f676a7ab0daa8fdecb0fd"
+  integrity sha512-8dG4H5ujfvFiqDmVu9fQ5bOHUC15JMjMY/Zumv26oOvvVJjM67KF8koCWIabKQ1GJIa9r2mMZscBq/TbdOcmNA==
+
+normalize-url@^4.1.0:
+  version "4.5.0"
+  resolved "https://registry.yarnpkg.com/normalize-url/-/normalize-url-4.5.0.tgz#453354087e6ca96957bd8f5baf753f5982142129"
+  integrity sha512-2s47yzUxdexf1OhyRi4Em83iQk0aPvwTddtFz4hnSSw9dCEsLEGf6SwIO8ss/19S9iBb5sJaOuTvTGDeZI00BQ==
+
+once@^1.3.1, once@^1.4.0:
+  version "1.4.0"
+  resolved "https://registry.yarnpkg.com/once/-/once-1.4.0.tgz#583b1aa775961d4b113ac17d9c50baef9dd76bd1"
+  integrity sha1-WDsap3WWHUsROsF9nFC6753Xa9E=
+  dependencies:
+    wrappy "1"
+
+p-cancelable@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/p-cancelable/-/p-cancelable-2.0.0.tgz#4a3740f5bdaf5ed5d7c3e34882c6fb5d6b266a6e"
+  integrity sha512-wvPXDmbMmu2ksjkB4Z3nZWTSkJEb9lqVdMaCKpZUGJG9TMiNp9XcbG3fn9fPKjem04fJMJnXoyFPk2FmgiaiNg==
+
+parse-github-url@1.0.2:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/parse-github-url/-/parse-github-url-1.0.2.tgz#242d3b65cbcdda14bb50439e3242acf6971db395"
+  integrity sha512-kgBf6avCbO3Cn6+RnzRGLkUsv4ZVqv/VfAYkRsyBcgkshNvVBkRn1FEZcW0Jb+npXQWm2vHPnnOqFteZxRRGNw==
+
+pump@^3.0.0:
+  version "3.0.0"
+  resolved "https://registry.yarnpkg.com/pump/-/pump-3.0.0.tgz#b4a2116815bde2f4e1ea602354e8c75565107a64"
+  integrity sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==
+  dependencies:
+    end-of-stream "^1.1.0"
+    once "^1.3.1"
+
+readable-stream@^3.0.1, readable-stream@^3.1.1:
+  version "3.4.0"
+  resolved "https://registry.yarnpkg.com/readable-stream/-/readable-stream-3.4.0.tgz#a51c26754658e0a3c21dbf59163bd45ba6f447fc"
+  integrity sha512-jItXPLmrSR8jmTRmRWJXCnGJsfy85mB3Wd/uINMXA65yrnFo0cPClFIUWzo2najVNSl+mx7/4W8ttlLWJe99pQ==
+  dependencies:
+    inherits "^2.0.3"
+    string_decoder "^1.1.1"
+    util-deprecate "^1.0.1"
+
+responselike@^2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/responselike/-/responselike-2.0.0.tgz#26391bcc3174f750f9a79eacc40a12a5c42d7723"
+  integrity sha512-xH48u3FTB9VsZw7R+vvgaKeLKzT6jOogbQhEe/jewwnZgzPcnyWui2Av6JpoYZF/91uueC+lqhWqeURw5/qhCw==
+  dependencies:
+    lowercase-keys "^2.0.0"
+
+safe-buffer@~5.2.0:
+  version "5.2.0"
+  resolved "https://registry.yarnpkg.com/safe-buffer/-/safe-buffer-5.2.0.tgz#b74daec49b1148f88c64b68d49b1e815c1f2f519"
+  integrity sha512-fZEwUGbVl7kouZs1jCdMLdt95hdIv0ZeHg6L7qPeciMZhZ+/gdesW4wgTARkrFWEpspjEATAzUGPG8N2jJiwbg==
+
+string_decoder@^1.1.1:
+  version "1.3.0"
+  resolved "https://registry.yarnpkg.com/string_decoder/-/string_decoder-1.3.0.tgz#42f114594a46cf1a8e30b0a84f56c78c3edac21e"
+  integrity sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==
+  dependencies:
+    safe-buffer "~5.2.0"
+
+tar-fs@2.0.0:
+  version "2.0.0"
+  resolved "https://registry.yarnpkg.com/tar-fs/-/tar-fs-2.0.0.tgz#677700fc0c8b337a78bee3623fdc235f21d7afad"
+  integrity sha512-vaY0obB6Om/fso8a8vakQBzwholQ7v5+uy+tF3Ozvxv1KNezmVQAiWtcNmMHFSFPqL3dJA8ha6gdtFbfX9mcxA==
+  dependencies:
+    chownr "^1.1.1"
+    mkdirp "^0.5.1"
+    pump "^3.0.0"
+    tar-stream "^2.0.0"
+
+tar-stream@^2.0.0:
+  version "2.1.0"
+  resolved "https://registry.yarnpkg.com/tar-stream/-/tar-stream-2.1.0.tgz#d1aaa3661f05b38b5acc9b7020efdca5179a2cc3"
+  integrity sha512-+DAn4Nb4+gz6WZigRzKEZl1QuJVOLtAwwF+WUxy1fJ6X63CaGaUAxJRD2KEn1OMfcbCjySTYpNC6WmfQoIEOdw==
+  dependencies:
+    bl "^3.0.0"
+    end-of-stream "^1.4.1"
+    fs-constants "^1.0.0"
+    inherits "^2.0.3"
+    readable-stream "^3.1.1"
+
+to-readable-stream@^2.0.0:
+  version "2.1.0"
+  resolved "https://registry.yarnpkg.com/to-readable-stream/-/to-readable-stream-2.1.0.tgz#82880316121bea662cdc226adb30addb50cb06e8"
+  integrity sha512-o3Qa6DGg1CEXshSdvWNX2sN4QHqg03SPq7U6jPXRahlQdl5dK8oXjkU/2/sGrnOZKeGV1zLSO8qPwyKklPPE7w==
+
+"traverse@>=0.3.0 <0.4":
+  version "0.3.9"
+  resolved "https://registry.yarnpkg.com/traverse/-/traverse-0.3.9.tgz#717b8f220cc0bb7b44e40514c22b2e8bbc70d8b9"
+  integrity sha1-cXuPIgzAu3tE5AUUwisui7xw2Lk=
+
+tslib@^1.9.3:
+  version "1.10.0"
+  resolved "https://registry.yarnpkg.com/tslib/-/tslib-1.10.0.tgz#c3c19f95973fb0a62973fb09d90d961ee43e5c8a"
+  integrity sha512-qOebF53frne81cf0S9B41ByenJ3/IuH8yJKngAX35CmiZySA0khhkovshKK+jGCaMnVomla7gVlIcc3EvKPbTQ==
+
+type-fest@^0.8.0:
+  version "0.8.1"
+  resolved "https://registry.yarnpkg.com/type-fest/-/type-fest-0.8.1.tgz#09e249ebde851d3b1e48d27c105444667f17b83d"
+  integrity sha512-4dbzIzqvjtgiM5rw1k5rEHtBANKmdudhGyBEajN01fEyhaAIhsoKNy6y7+IN93IfpFtwY9iqi7kD+xwKhQsNJA==
+
+typescript@3.7.4:
+  version "3.7.4"
+  resolved "https://registry.yarnpkg.com/typescript/-/typescript-3.7.4.tgz#1743a5ec5fef6a1fa9f3e4708e33c81c73876c19"
+  integrity sha512-A25xv5XCtarLwXpcDNZzCGvW2D1S3/bACratYBx2sax8PefsFhlYmkQicKHvpYflFS8if4zne5zT5kpJ7pzuvw==
+
+unzip-stream@0.3.0:
+  version "0.3.0"
+  resolved "https://registry.yarnpkg.com/unzip-stream/-/unzip-stream-0.3.0.tgz#c30c054cd6b0d64b13a23cd3ece911eb0b2b52d8"
+  integrity sha512-NG1h/MdGIX3HzyqMjyj1laBCmlPYhcO4xEy7gEqqzGiSLw7XqDQCnY4nYSn5XSaH8mQ6TFkaujrO8d/PIZN85A==
+  dependencies:
+    binary "^0.3.0"
+    mkdirp "^0.5.1"
+
+util-deprecate@^1.0.1:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/util-deprecate/-/util-deprecate-1.0.2.tgz#450d4dc9fa70de732762fbd2d4a28981419a0ccf"
+  integrity sha1-RQ1Nyfpw3nMnYvvS1KKJgUGaDM8=
+
+wrappy@1:
+  version "1.0.2"
+  resolved "https://registry.yarnpkg.com/wrappy/-/wrappy-1.0.2.tgz#b5243d8f3ec1aa35f1364605bc0d1036e30ab69f"
+  integrity sha1-tSQ9jz7BqjXxNkYFvA0QNuMKtp8=

codecov.yml

@@ -0,0 +1,8 @@
+codecov:
+  require_ci_to_pass: yes
+
+coverage:
+  status:
+    project: off
+    patch: off
+

errors/deploy-invalid-dc.md

@@ -2,8 +2,8 @@
 
 #### Why This Error Occurred
 
-When supplying `regions` configuration, you
-used an unknown or invalid DC identifier.
+When supplying `regions` or `scale` settings, you
+used an unknown or invalid dc identifier.
 
 #### Possible Ways to Fix It
 
@@ -19,7 +19,7 @@ and DCs have to be in _lowercase_.
 - `gru`
 - `iad`
 
-In Vercel 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**:
@@ -33,5 +33,5 @@ When passing multiple `--regions` as a CLI parameter,
 make sure they're separated by a comma (`,`). For example:
 
 ```console
-vercel --regions sfo,bru,gru
+now --regions sfo,bru,gru
 ```

errors/deployment-error.md

@@ -1,13 +0,0 @@
-# Deployment failed
-
-## Why This Error Occurred
-
-When deploying this project, there was not a successful deployment into the `READY` state.
-
-## How to Fix It
-
-This is a generic error to catch problems in the deployment. The error is likely to vary depending on the deployment and the conditions at the time.
-
-Try looking in the logs for information about the deployment and the failure, this could be done at (vercel.com)[https://vercel.com]. You can also use the `vc logs` command to display the build logs for the deployment.
-
-This might not be a permanent error and retrying the deployment might also resolve it.

errors/domain-verification.md

@@ -2,18 +2,20 @@
 
 #### Why This Error Occurred
 
-The domain you supplied cannot be verified using the intended nameservers.
+The domain you supplied cannot be verified using either the intended set of nameservers or the given verification TXT record.
 
-#### Possible Way to Fix It
+#### Possible Ways to Fix It
 
-Apply the intended set of nameservers to your domain.
+Apply the intended set of nameservers to your domain or add the given TXT verification record through your domain provider.
 
-You can retrieve both the intended nameservers and TXT verification record for the domain you wish to verify by running `vercel domains inspect <domain>`.
+You can retrieve both the intended nameservers and TXT verification record for the domain you wish to verify by running `now domains inspect <domain>`.
+
+When you have added either verification method to your domain, you can run `now domains verify <domain>` again to complete verification for your 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 `vercel domains rm <domain>`.
+If you would not like to verify your domain, you can remove it from your account using `now domains rm <domain>`.
 
 #### Resources
 
-- [Vercel Custom Domains Documentation](https://vercel.com/docs/concepts/projects/custom-domains)
+- [Vercel Custom Domains Documentation](https://vercel.com/docs/v2/custom-domains)

errors/env-no-secret.md

@@ -9,9 +9,9 @@ You specified the `--env` or `-e` flag with the value of a secret. However, the
 Make sure to specify the environment variable and secret like that:
 
 ```bash
-vercel -e VARIABLE_NAME=@secret-name
+now -e VARIABLE_NAME=@secret-name
 ```
 
 In addition, ensure that the secret (`@secret-name` in the example above) exists in the current scope (the team or user account that you're using).
 
-You can run `vercel switch` or `--scope` to switch to a different team or user.
+You can run `now switch` or `--scope` to switch to a different team or user.

errors/missing-dotenv-target.md

@@ -0,0 +1,9 @@
+# Missing `--dotenv` Target
+
+#### Why This Error Occurred
+
+You specified a path as the value for the `--dotenv` flag, but the target of the path doesn't exist.
+
+#### Possible Ways to Fix It
+
+Make sure the target file you've specified exists and is readable by Now CLI. In addition, please ensure that the filename starts with a dot (example: `.env`) - then it should work.

errors/missing-env-file.md

@@ -2,21 +2,21 @@
 
 #### Why This Error Occurred
 
-You ran `vercel dev` inside a project that contains a `vercel.json` file with `env` or `build.env` properties that use [Vercel Secrets](https://vercel.com/docs/concepts/projects/environment-variables).
+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 Vercel Secrets format (e.g. `@my-secret-value`), you will need to provide the value as an environment variable using a `.env.local`.
+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.
 
-We require this to ensure your app works as you intend it to, in the development environment, and to provide you with a way to mirror or separate private environment variables within your applications, for example when connecting to a database.
+We require this to ensure your app works as you intend it to, in the Now Dev environment, and to provide you with a way to mirror or separate private environment variables within your applications, for example when connecting to a database.
 
 Read below for how to address this error.
 
 #### Possible Ways to Fix It
 
-The error message will list environment variables that are required and which file they are required to be included in `.env.local`.
+The error message will list environment variables that are required and which file they are required to be included in (either `.env` or `.env.build`).
 
 If the file does not exist yet, please create the file that the error message mentions and insert the missing environment variable into it.
 
-For example, if the error message shows that the environment variable `TEST` is missing from `.env.local`, then the `.env.local` file should look like this:
+For example, if the error message shows that the environment variable `TEST` is missing from `.env`, then the `.env` file should look like this:
 
 ```
 TEST=value
@@ -24,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://vercel.com/docs/concepts/projects/environment-variables).
+For more information on Environment Variables in development, [see the documentation](https://vercel.com/docs/v2/build-step#environment-variables).

errors/missing-env-key-value.md

@@ -9,11 +9,11 @@ You specified the `--env` or `-e` flag and didn't add a name and value for the e
 Make sure to set the name and value of the variable like this:
 
 ```bash
-vercel -e VARIABLE_NAME="VALUE"
+now -e VARIABLE_NAME="VALUE"
 ```
 
 You can also specify a environment variable that contains a secret:
 
 ```bash
-vercel -e VARIABLE_NAME=@secret-name
+now -e VARIABLE_NAME=@secret-name
 ```

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://vercel.com/my-team`, you would set `--scope` to `my-team`.
+As an example, if your team URL is `https://vercel.com/teams/zeit`, you would set `--scope` to `zeit`.

errors/next-functions-config-optimized-lambdas.md

@@ -1,14 +0,0 @@
-# `@vercel/next` Functions Config Optimized Lambdas Opt-out
-
-#### Why This Warning Occurred
-
-`@vercel/next` by default now bundles pages into optimized functions, minimizing bootup time and increasing overall application throughput.
-When the `functions` config is added in `now.json` or `vercel.json`, it causes conflicts with this optimization, so it is opted-out.
-
-#### Possible Ways to Fix It
-
-Remove the `functions` config from your `now.json` or `vercel.json` to take advantage of this optimization.
-
-### Useful Links
-
-- [Functions Config Documentation](https://vercel.com/docs/concepts/projects/project-configuration#functions)

errors/next-legacy-routes-optimized-lambdas.md

@@ -1,16 +0,0 @@
-# `@vercel/next` Legacy Routes Optimized Lambdas Opt-out
-
-#### Why This Warning Occurred
-
-`@vercel/next` by default now bundles pages into optimized functions, minimizing bootup time and increasing overall application throughput.
-When legacy `routes` are added in `now.json` or `vercel.json`, they cause conflicts with this optimization, so it is opted-out.
-
-#### Possible Ways to Fix It
-
-Migrate from using legacy `routes` to the new `rewrites`, `redirects`, and `headers` configurations in your `now.json` or `vercel.json` file or leverage them directly in your `next.config.js` with the built-in [custom routes support](https://github.com/vercel/next.js/issues/9081)
-
-### Useful Links
-
-- [Rewrites Documentation](https://vercel.com/docs/concepts/projects/project-configuration#rewrites)
-- [Redirects Documentation](https://vercel.com/docs/concepts/projects/project-configuration#redirects)
-- [Headers Documentation](https://vercel.com/docs/concepts/projects/project-configuration#headers)

errors/no-credentials-found.md

@@ -2,9 +2,9 @@
 
 #### Why This Error Occurred
 
-You're running Vercel CLI in a non-terminal context and there are no credentials available. This means that Vercel CLI is not able to authenticate against our service.
+You're running Now CLI in a non-terminal context and there are no credentials available. This means that Now CLI is not able to authenticate against our service.
 
 #### 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 create a new token on your [Settings page](https://vercel.com/account/tokens).
-- Run `vercel login` to sign in and generate a new token
+- 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-single-file-deployments.md

@@ -1,9 +0,0 @@
-# No Single File Deployments
-
-#### Why This Error Occurred
-
-You attempted to create a Vercel deployment where the input is a file, rather than a directory. Previously this was allowed, however this behavior has been removed as of Vercel CLI v24.0.0 because it exposed a potential security risk if the user accidentally created a deployment from a sensitive file.
-
-#### Possible Ways to Fix It
-
-- Run the `vercel deploy` command against a directory, instead of a file.

errors/no-token-allowed.md

@@ -2,10 +2,10 @@
 
 #### Why This Error Occurred
 
-You tried to run a command that doesn't allow the `--token` flag (like `vercel switch`). This is not allowed because commands like these are influencing the configuration files.
+You tried to run a command that doesn't allow the `--token` flag (like `now switch`). This is not allowed because commands like these are influencing the configuration files.
 
-In turn, they would have to take the value of the `--token` flag into consideration (which is not a good idea, because flags in Vercel CLI should never change the configuration).
+In turn, they would have to take the value of the `--token` flag into consideration (which is not a good idea, because flags in Now CLI should never change the configuration).
 
 #### 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://vercel.com/my-team`, the value can be `my-team`) 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-dev-as-dev-script.md

@@ -1,8 +1,8 @@
-# `vercel dev` as `dev` script
+# `now dev` as `dev` script
 
 #### Why This Error Occurred
 
-The `package.json` file of the used project invokes `vercel dev` as `dev` script. This would cause `vercel dev` to recursively invoke itself.
+The `package.json` file of the used project invokes `now dev` as `dev` script. This would cause `now dev` to recursively invoke itself.
 
 #### Possible Ways to Fix It
 

errors/now-next-legacy-mode.md

@@ -1,8 +1,8 @@
-# `@vercel/next` Legacy Mode
+# `@now/next` Legacy Mode
 
 #### Why This Warning Occurred
 
-`@vercel/next` has two modes: `legacy` and `serverless`. You will always want to use the `serverless` mode. `legacy` is to provide backwards compatibility with previous `@vercel/next` versions.
+`@now/next` has two modes: `legacy` and `serverless`. You will always want to use the `serverless` mode. `legacy` is to provide backwards compatibility with previous `@now/next` versions.
 
 The differences:
 
@@ -20,14 +20,14 @@ Legacy:
 Serverless:
 
 - Minimal lambda size of `49Kb` (approximately)
-- Uses Next.js build targets (`target: 'serverless'`) in `next.config.js`. [documentation](https://github.com/vercel/next.js#summary)
+- Uses Next.js build targets (`target: 'serverless'`) in `next.config.js`. [documentation](https://github.com/zeit/next.js#summary)
 - Does not make changes to your application dependencies
-- Does not load `next.config.js` ([as per the serverless target documentation](https://github.com/vercel/next.js#summary))
+- Does not load `next.config.js` ([as per the serverless target documentation](https://github.com/zeit/next.js#summary))
 - Runs `npm install`
 - 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
+- Optimized for fast [cold start](https://vercel.com/blog/serverless-ssr#cold-start)
 
 #### Possible Ways to Fix It
 
@@ -63,10 +63,10 @@ module.exports = {
 ```js
 {
   "version": 2,
-  "builds": [{ "src": "package.json", "use": "@vercel/next" }]
+  "builds": [{ "src": "package.json", "use": "@now/next" }]
 }
 ```
 
 ### Useful Links
 
-- [Serverless target implementation](https://github.com/vercel/now-builders/pull/150)
+- [Serverless target implementation](https://github.com/zeit/now-builders/pull/150)

errors/now-next-no-serverless-pages-built.md

@@ -1,8 +1,8 @@
-# `@vercel/next` No Serverless Pages Built
+# `@now/next` No Serverless Pages Built
 
 #### Why This Error Occurred
 
-This error occurs when your application is not configured for Serverless Next.js build output.
+This error occurs when you have your application is not configured for Serverless Next.js build output.
 
 #### Possible Ways to Fix It
 
@@ -14,9 +14,7 @@ In order to create the smallest possible lambdas Next.js has to be configured to
 npm install next --save
 ```
 
-2. Check [Node.js Version](https://vercel.link/node-version) in your Project Settings. Using an old or incompatible version of Node.js can cause the Build Step to fail with this error message.
-
-3. Add the `now-build` script to your `package.json` [deprecated]
+2. Add the `now-build` script to your `package.json`
 
 ```json
 {
@@ -26,7 +24,7 @@ npm install next --save
 }
 ```
 
-4. Add `target: 'serverless'` to `next.config.js` [deprecated]
+3. Add `target: 'serverless'` to `next.config.js`
 
 ```js
 module.exports = {
@@ -35,15 +33,13 @@ module.exports = {
 };
 ```
 
-5. Remove `distDir` from `next.config.js` as `@vercel/next` can't parse this file and expects your build output at `/.next`
+4. Remove `distDir` from `next.config.js` as `@now/next` can't parse this file and expects your build output at `/.next`
 
-6. Optionally make sure the `"src"` in `"builds"` points to your application `package.json`
+5. Optionally make sure the `"src"` in `"builds"` points to your application `package.json`
 
 ```js
 {
   "version": 2,
-  "builds": [{ "src": "package.json", "use": "@vercel/next" }]
+  "builds": [{ "src": "package.json", "use": "@now/next" }]
 }
 ```
-
-6. Make sure you have the correct Node.js version selected for your build step in your project settings (`https://vercel.com/[username]/[project]/settings`)

errors/now-next-routes-manifest.md

@@ -2,15 +2,10 @@
 
 #### Why This Error Occurred
 
-This error is often caused by a misconfigured "Build Command" or "Output Directory" for your Next.js project.
+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
 
-In the Vercel dashboard, open your "Project Settings" and draw attention to "Build & Development Settings":
+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`).
 
-1. Ensure that the "Build Command" setting is not overridden, or that it calls `next build`. If this command is not overridden but you are seeing this error, double check that your `build` script in `package.json` calls `next build`. If `buildCommand` exists in `vercel.json`, make sure it calls `next build`.
-2. Ensure that the "Output Directory" setting is not overridden. This value almost never needs to be configured, and is only necessary if you override `distDir` in `next.config.js`. If `outputDirectory` exists in `vercel.json`, remove that property.
-3. For `next export` users: **do not override the "Output Directory"**, even if you customized the `next export` output directory. It will automatically detects the correct output.
-
-In rare scenarios, this error message can also be caused by a Next.js build failure (if your "Build Command" accidentally returns an exit code that is not 0).
-Double check for any error messages above the Routes Manifest error, which may provide additional details.
+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

@@ -1,22 +1,22 @@
-# `@vercel/static-build` Failed to detect a server running
+# `@now/static-build` Failed to detect a server running
 
 #### Why This Warning Occurred
 
-When running `vercel dev`, the `@vercel/static-build` builder proxies relevant HTTP
-requests to the server that is created by the `dev` script in the
+When running `now dev`, the `@now/static-build` builder proxies relevant HTTP
+requests to the server that is created by the `now-dev` script in the
 `package.json` file.
 
-In order for `vercel dev` to know which port the server is running on, the builder
+In order for `now dev` to know which port the server is running on, the builder
 is provided a `$PORT` environment variable that the server _must_ bind to. The
 error "Failed to detect a server running on port" is printed if the builder fails
 to detect a server listening on that specific port within five minutes.
 
 #### Possible Ways to Fix It
 
-Please ensure that your `dev` script binds the spawned development server on
+Please ensure that your `now-dev` script binds the spawned development server on
 the provided `$PORT` that the builder expects the server to bind to.
 
-For example, if you are using Gatsby, your `dev` script must use the `-p`
+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%`_
@@ -26,7 +26,7 @@ For example, if you are using Gatsby, your `dev` script must use the `-p`
   ...
   "scripts": {
     ...
-    "dev": "gatsby develop -p $PORT"
+    "now-dev": "gatsby develop -p $PORT"
   }
 }
 ```

errors/path-not-deployable.md

@@ -2,7 +2,7 @@
 
 #### Why This Error Occurred
 
-You either tried to run Vercel CLI inside a directory that should never be deployed, or you specified a directory that should never be deployed like this: `vercel <directory>`.
+You either tried to run Now CLI inside a directory that should never be deployed, or you specified a directory that should never be deployed like this: `now <directory>`.
 
 #### Possible Ways to Fix It
 

errors/regions-and-scale-at-once.md

@@ -0,0 +1,32 @@
+# Can't Set `regions` and `scale` Options Simultaneously
+
+#### Why This Error Occurred
+
+Your deployment's configuration contains a `regions` and `scale`
+configuration simultaneously.
+
+#### Possible Ways to Fix It
+
+The `regions` setting is intended to be used to scale the
+deployment to the supplied regions or datacenters identifiers
+with default scale settings.
+
+```json
+{
+  "regions": ["sfo", "bru", "gru", "iad"]
+}
+```
+
+The `scale` object allows you to be more granular: you can decide a
+`min` and `max` number of instances per region:
+
+```json
+{
+  "scale": {
+    "sfo": { "min": 0, "max": 10 }
+  }
+}
+```
+
+To solve this problem, use only one of the two ways of deciding
+where to scale your deployment to.

errors/scale-invalid-dc.md

@@ -0,0 +1,36 @@
+# Invalid Region or DC Identifier
+
+#### Why This Error Occurred
+
+When supplying a region or DC identifier in `now scale`,
+we weren't able to recognize the value as valid.
+
+#### Possible Ways to Fix It
+
+Check your `now scale` command make sure you are using a
+valid string after the URL. Regions
+and DCs have to be in *lowercase*.
+
+**Valid region identifiers**:
+
+- `all` (special, used to scale to all DCs, can only appear once)
+- `sfo`
+- `bru`
+- `gru`
+- `iad`
+
+In `now-cli`, they currently are transformed to
+DC identifiers before being sent to our APIs.
+
+**Valid DC identifiers**:
+
+- `sfo1`
+- `bru1`
+- `gru1`
+- `iad1`
+
+To pass multiple ones, use a comma:
+
+```
+now scale my-url-123.now.sh sfo,bru,gru 1 5
+```

errors/scale-ls.md

@@ -0,0 +1,31 @@
+# `now scale ls` is deprecated
+
+#### Why This Error Occurred
+
+We have stopped supporting this command, in favor of
+better alternatives.
+
+`now scale ls` used to list all the scaling rules
+for all your deployments. The output would be too long,
+and it would often be hard to find the information
+you needed in a long list of items.
+
+#### Possible Ways to Fix It
+
+Instead of using `now scale ls` to list all your deployments
+and their scaling rules, first use `now ls` to find
+your deployment:
+
+```console
+now ls
+```
+
+Then, select the URL of your deployment, which uniquely identifies it, and run:
+
+```console
+now inspect my-deployment-12345.now.sh
+```
+
+The `inspect` subcommand will give you your deployment's scale information, including what datacenters it's enabled on, the
+current number of instances and minimums/maximums.
+

errors/scaling-path-alias.md

@@ -0,0 +1,12 @@
+# Scaling path alias
+
+#### Why This Error Occurred
+
+You tried to use `now scale` on a path alias (`now alias -r rules.json`). 
+
+#### Possible Ways to Fix It
+
+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://vercel.com/docs/features/path-aliases).

errors/scope-not-accessible.md

@@ -6,6 +6,5 @@ You specified the `--scope` flag and specified the ID or slug of a team that you
 
 #### Possible Ways to Fix It
 
-- Make sure commands like `vercel ls` work just fine. This will ensure that your user credentials are valid. If it's not working correctly, please log in again using `vercel login`.
-- If you're using the `--token` flag, make sure your token is not expired. You can generate a new token on your [Settings page](https://vercel.com/account/tokens).
-- Ensure that the scope you specified using `--scope` flag shows up in the output of `vercel switch`. If it doesn't, you're either not a member of the team or you logged into the wrong user account. You can ask an owner of the team to invite you.
+- Make sure commands like `now ls` work just fine. This will ensure that your user credentials are valid. If it's not working correctly, please log in again using `now login`.
+- Ensure that the scope you specified using `--scope` shows up in the output of `now switch`. If it doesn't, you're either not part of the team (if you specified a team) or you logged into the wrong user account.

errors/scope-not-existent.md

@@ -2,10 +2,10 @@
 
 #### Why This Error Occurred
 
-You specified the `--scope` flag and specified the ID or slug of a team that does not exist or that you're not a member. Similarly you might have specified the ID or username of user whose account you don't own.
+You specified the `--scope` flag and specified the ID or slug of a team that does not exist or that you're not a part of. Similarly you might have specified the ID or username of user whose account you don't own.
 
 #### Possible Ways to Fix It
 
-- Make sure commands like `vercel ls` work just fine. This will ensure that your user credentials are valid. If it's not working correctly, please log in again using `vercel login`.
-- If you're using the `--token` flag, make sure your token is not expired. You can generate a new token on your [Settings page](https://vercel.com/account/tokens).
-- Ensure that the scope you specified using `--scope` flag shows up in the output of `vercel switch`. If it doesn't, you're either not a member of the team or you logged into the wrong user account. You can ask an owner of the team to invite you.
+If you're sure the specified team exists, please make sure that you're a part of it (ask an owner of the team to invite you). If you specified the identifier of a user, make sure you are actually the owner of this account.
+
+Otherwise, either create a team with the specified slug or ensure that the identifier is correct if you're sure that the scope exists.

errors/unauthorized-domain.md

@@ -6,4 +6,4 @@ You tried to add or update a domain's configuration, but you don't have permissi
 
 #### Possible Ways to Fix It
 
-If you or your team owns the domain, then you are most likely in the wrong context. Use `vercel switch` to select the team or user that owns the domain.
+If you or your team owns the domain, then you are most likely in the wrong context. Use `now switch` to select the team or user that owns the domain.

errors/v2-no-min.md

@@ -0,0 +1,16 @@
+# No minimum scale settings on Cloud v2 deployments
+
+#### Why This Error Occurred
+
+An attempt was made at scaling a Cloud v2 deployment with a `min` scale
+setting. This isn't supported yet.
+
+#### Possible Ways to Fix It
+
+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
+
+```
+now scale <deployment> 0 10
+```

errors/verification-timeout.md

@@ -0,0 +1,29 @@
+# Verification Timeout
+
+#### Why This Error Occurred
+
+After the deployment build completed and the deployment state was set to `READY`,
+instances failed to initialize properly.
+
+The CLI attempted to verify that the scale settings of your instances matched,
+but it couldn't do so within the allotted time (defaults to 2 minutes).
+
+#### Possible Ways to Fix It
+
+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://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
+to slow boot up times. You can supply `--no-verify` to skip verification
+if you are confident your code runs properly.
+
+If your application is not listening on a HTTP port, we might be failing to 
+instantiate your deployment as well. It might not be showing any errors,
+but the deployment instance is effectively not routable and cannot be
+verified.
+
+If your instances are crashing before an HTTP port is exposed, verification
+will fail as well. Double check your logs (e.g.: by running `now logs <url>`)

examples/CHANGELOG.md

@@ -1,13 +0,0 @@
-# examples
-
-## null
-
-### Patch Changes
-
-- chore: update Nuxt example ([#10869](https://github.com/vercel/vercel/pull/10869))
-
-## null
-
-### Patch Changes
-
-- update examples to use at least node@16 ([#10395](https://github.com/vercel/vercel/pull/10395))

examples/README.md

@@ -1,39 +1,85 @@
 # Vercel Examples
 
-To get started using any of these examples as your own project, [install Vercel](https://vercel.com/cli) and use either of the following commands in your terminal:
+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 Vercel?
+
+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 [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
+- [License](https://github.com/zeit/now/blob/master/LICENSE) - the standard MIT license under which these examples are published
+
+We recommend familiarizing yourself with the above sections, particularly if you are looking to make a contribution.
+
+## Deploying Examples
+
+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
-vercel init                    # Pick an example in the CLI
-vercel init <example>          # Create a new project from a specific <example>
-vercel init <example> <name>   # Create a new project from a specific <example> with a different folder <name>
+now init                    # Pick an example in the CLI
+now init <example>          # Create a new project from a specific <example>
+now init <example> <name>   # Create a new project from a specific <example> with a different folder <name>
 ```
 
-Deploying your project can be done with **a single command**:
+Deploying your project takes seconds and can be done with **just a single command**:
 
 ```sh
-vercel                         # Deploy your project with the CLI
+now                         # Deploys the project with Now
 ```
 
-With the `vercel` command, your project will be built and served by Vercel, providing you with a URL that can be shared immediately.
+With the `now` command, your project will be built and served by Now, providing you with a URL that can be shared immediately.
+
+## New Examples
+
+We are continuously improving our examples based on best practices and feedback from the community. As a result, it is possible that example names will change and on occasion deprecated in favor of an improved implementation.
+
+For example, the previous `nodejs` example showed a static frontend with a Node.js API. This is illustrated now in the `svelte` example. Below is a table that lists some of the most popular previous examples and the equivalent replacement:
+
+| Previous Example  | New Example                                                                           |
+| ----------------- | ------------------------------------------------------------------------------------- |
+| **monorepo**      | [gatsby-functions](https://github.com/zeit/now/tree/master/examples/gatsby)           |
+| **nodejs**        | [svelte-functions](https://github.com/zeit/now/tree/master/examples/svelte)           |
+| **nextjs-static** | [nextjs](https://github.com/zeit/now/tree/master/examples/nextjs)                     |
+| **vanilla-go**    | [create-react-app](https://github.com/zeit/now/tree/master/examples/create-react-app) |
+| **typescript**    | [gatsby-functions](https://github.com/zeit/now/tree/master/examples/gatsby)           |
+
+## Migrating and Upgrading
+
+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://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
 
-Contributing examples should be an enjoyable experience, as such we have created a set of [contributing guidelines](https://github.com/vercel/vercel/blob/main/.github/CONTRIBUTING.md) to help you do so.
+Contributing to Now Examples should be an enjoyable experience, as such we have created a set of [contributing guidelines](https://github.com/zeit/docs/blob/master/CONTRIBUTING.md) to help you do so.
 
 The guidelines cover important information such as the requirements for new examples and where to get help if you have any questions.
 
-We have tried to make contributing to examples as easy as possible, especially for those new to Open Source. If anything is unclear or you have any questions then please reach out to us on [GitHub Discussions](https://github.com/vercel/vercel/discussions) where we will do our best to help you.
+We have tried to make contributing to Now Examples as easy as possible, especially for those new to Open Source. If anything is unclear or you have any questions then please reach out to us on [GitHub Discussions](https://github.com/zeit/now/discussions) where we will do our best to help you.
 
 ## Reporting Issues
 
-We actively encourage our community to raise issues and provide feedback on areas of examples that could be improved.
+We actively encourage our community to raise issues and provide feedback on areas of Now Examples that could be improved.
 
 An issue can be raised by clicking the 'Issues' tab at the top of the repository, followed by the Green 'New issue' button.
 
 When submitting an issue, please thoroughly and concisely describe the problem you are experiencing so that we may easily understand and resolve the issue in a timely manner.
 
+## License
+
+Now Examples is an open source project released under the [MIT License](https://github.com/zeit/docs/blob/master/LICENSE.md).
+
 ## 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/vercel/vercel/discussions). There you will find both members of the community and staff who are happy to help answer questions on anything Vercel 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/vercel/vercel/discussions)
+[![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/__tests__/integration/angular.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy angular', async () => {
-  await deployExample('angular');
-});

examples/__tests__/integration/astro.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy astro', async () => {
-  await deployExample('astro');
-});

examples/__tests__/integration/blitzjs.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy blitzjs', async () => {
-  await deployExample('blitzjs');
-});

examples/__tests__/integration/brunch.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy brunch', async () => {
-  await deployExample('brunch');
-});

examples/__tests__/integration/create-react-app.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy create-react-app', async () => {
-  await deployExample('create-react-app');
-});

examples/__tests__/integration/docusaurus-2.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy docusaurus-2', async () => {
-  await deployExample('docusaurus-2');
-});

examples/__tests__/integration/docusaurus.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy docusaurus', async () => {
-  await deployExample('docusaurus');
-});

examples/__tests__/integration/dojo.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy dojo', async () => {
-  await deployExample('dojo');
-});

examples/__tests__/integration/eleventy.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy eleventy', async () => {
-  await deployExample('eleventy');
-});

examples/__tests__/integration/ember.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy ember', async () => {
-  await deployExample('ember');
-});

examples/__tests__/integration/gatsby.test.ts

@@ -1,4 +0,0 @@
-import { deployExample } from '../test-utils';
-it('[examples] should deploy gatsby', async () => {
-  await deployExample('gatsby');
-});