Publish Stable

- @vercel/build-utils@6.3.2
 - vercel@28.16.8
 - @vercel/client@12.4.2
 - @vercel/edge@0.3.1
 - @vercel/frameworks@1.3.2
 - @vercel/fs-detectors@3.8.2
 - @vercel/gatsby-plugin-vercel-builder@1.1.10
 - @vercel/go@2.3.9
 - @vercel/hydrogen@0.0.55
 - @vercel/next@3.6.2
 - @vercel/node-bridge@3.1.13
 - @vercel/node@2.9.9
 - @vercel/python@3.1.51
 - @vercel/redwood@1.1.7
 - @vercel/remix@1.4.2
 - @vercel/routing-utils@2.1.10
 - @vercel/ruby@1.3.68
 - @vercel/static-build@1.3.13

.editorconfig

@@ -0,0 +1,42 @@
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+tab_width = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true
+
+[{*.json,*.json.example,*.gyp,*.yml,*.yaml}]
+indent_style = space
+indent_size = 2
+
+[{*.py,*.asm}]
+indent_style = space
+
+[*.py]
+indent_size = 4
+
+[*.go]
+indent_style = tab
+indent_size = 4
+tab_width = 4
+
+[*.asm]
+indent_size = 8
+
+[*.md]
+trim_trailing_whitespace = false
+
+# Ideal settings - some plugins might support these.
+[*.js]
+quote_type = single
+
+[{*.c,*.cc,*.h,*.hh,*.cpp,*.hpp,*.m,*.mm,*.mpp,*.js,*.java,*.go,*.rs,*.php,*.ng,*.jsx,*.ts,*.d,*.cs,*.swift}]
+curly_bracket_next_line = false
+spaces_around_operators = true
+spaces_around_brackets = outside
+# close enough to 1TB
+indent_brace_style = K&R

.eslintignore

@@ -0,0 +1,50 @@
+node_modules
+dist
+examples
+
+packages/node/src/bridge.ts
+
+packages/*/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
+
+# client
+packages/client/tests/fixtures
+packages/client/lib
+
+# hydrogen
+packages/hydrogen/edge-entry.js
+
+# next
+packages/next/test/integration/middleware
+packages/next/test/integration/middleware-eval
+
+# node-bridge
+packages/node-bridge/bridge.js
+packages/node-bridge/launcher.js
+packages/node-bridge/helpers.js
+packages/node-bridge/source-map-support.js
+
+# middleware
+packages/middleware/src/entries.js
+
+# 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

.flowconfig

@@ -1,2 +0,0 @@
-[ignore]
-.*/node_modules/.*/\(test\).*\.json$

.gitattributes

@@ -0,0 +1,14 @@
+# Ignore test fixtures in GitHub Languages
+# See https://github.com/github/linguist#vendored-code
+examples/* linguist-vendored
+utils/* linguist-vendored
+test/* linguist-vendored
+packages/*/test/* linguist-vendored
+
+# Go build fails with Windows line endings.
+*.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

@@ -0,0 +1,16 @@
+# Documentation
+# https://help.github.com/en/articles/about-code-owners
+
+*                                        @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood
+/.github/workflows                       @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood @ijjk
+/packages/fs-detectors                   @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood @agadzik @chloetedder
+/packages/node-bridge                    @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood @ijjk
+/packages/next                           @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood @ijjk
+/packages/routing-utils                  @TooTallNate @EndangeredMassa @styfle @cb1kenobi @Ethan-Arrowood @ijjk
+/packages/edge                           @vercel/edge-compute
+/examples                                @leerob
+/examples/create-react-app               @Timer
+/examples/nextjs                         @timneutkens @ijjk @styfle
+/examples/hugo                           @styfle
+/examples/jekyll                         @styfle
+/examples/zola                           @styfle

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+## Code of Conduct
+
+### Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+### Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+### Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+### Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+### Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [coc@vercel.com](mailto:coc@vercel.com). All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+### Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,109 @@
+# 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.
+
+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.
+
+To get started, execute the following:
+
+```
+git clone https://github.com/vercel/vercel
+cd vercel
+corepack enable
+pnpm install
+pnpm bootstrap
+pnpm build
+pnpm lint
+pnpm test-unit
+```
+
+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:
+
+```
+pnpm test-unit
+```
+
+from the root of the project.
+
+If any test fails, make sure to fix it along with your changes. See [Interpreting test errors](#Interpreting-test-errors) for more information about how the tests are executed, especially the integration tests.
+
+## Pull Request Process
+
+Once you are confident that your changes work properly, open a pull request on the main repository.
+
+The pull request will be reviewed by the maintainers and the tests will be checked by our continuous integration platform.
+
+## Interpreting test errors
+
+There are 2 kinds of tests in this repository – Unit tests and Integration tests.
+
+Unit tests are run locally with `jest` and execute quickly because they are testing the smallest units of code.
+
+### Integration tests
+
+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.
+
+    NO_STATUS_CODE_FRO Response headers:
+       cache-control=s-maxage=0
+      connection=close
+      content-type=text/plain; charset=utf-8
+      date=Wed, 19 Jun 2019 18:01:37 GMT
+      server=now
+      strict-transport-security=max-age=63072000
+      transfer-encoding=chunked
+      x-now-id=iad1:hgtzj-1560967297876-44ae12559f95
+      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
+
+The logs of this deployment will contain the actual error which may help you to understand what went wrong.
+
+### @vercel/nft
+
+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:
+
+```js
+const { nodeFileTrace } = require('@vercel/nft');
+nodeFileTrace(['path/to/entrypoint.js'], {
+  ts: true,
+  mixedModules: true,
+})
+  .then(o => console.log(o.fileList))
+  .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.
+
+## 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.
+
+1. Change directory to the desired Builder `cd ./packages/node`
+2. Run `pnpm 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
+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

.github/EXAMPLE_README_TEMPLATE.md

@@ -0,0 +1,25 @@
+# [Name] Example
+
+This directory is a brief example of a [Name](site-link) site that can be deployed to Vercel with 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)
+
+### 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]]
+```
+
+### Deploying From Your Terminal
+
+Once initialized, you can deploy the [Name] example with just a single command:
+
+```shell
+$ vercel
+```

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Bug Report
+    url: https://vercel.com/support/request
+    about: Report a bug using the Vercel support form
+  - name: Feature Request
+    url: https://github.com/vercel/vercel/discussions/new?category=ideas
+    about: Share ideas for new features
+  - name: Ask a Question
+    url: https://github.com/vercel/vercel/discussions/new?category=help
+    about: Ask the community for help

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

@@ -0,0 +1,31 @@
+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

@@ -0,0 +1,31 @@
+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

@@ -0,0 +1,22 @@
+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

@@ -0,0 +1,24 @@
+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

@@ -0,0 +1,24 @@
+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,61 @@
+name: Publish
+
+on:
+  push:
+    branches:
+    - main
+    tags:
+    - '!*'
+
+env:
+  TURBO_REMOTE_ONLY: 'true'
+  TURBO_TEAM: 'vercel'
+  TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
+
+jobs:
+  publish:
+    name: Publish
+    runs-on: ubuntu-latest
+    steps:
+    - name: Checkout
+      uses: actions/checkout@v3
+      with:
+        fetch-depth: 0
+    - name: Check Release
+      id: check-release
+      run: |
+        tag="$(git describe --tags --exact-match 2> /dev/null || :)"
+        if [[ -z "$tag" ]];
+          then
+            echo "IS_RELEASE=false" >> $GITHUB_OUTPUT
+          else
+            echo "IS_RELEASE=true" >> $GITHUB_OUTPUT
+        fi
+    - name: Setup Go
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      uses: actions/setup-go@v3
+      with:
+        go-version: '1.13.15'
+    - name: Setup Node
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: 16
+    - name: install pnpm@7.24.2
+      run: npm i -g pnpm@7.24.2
+    - name: Install
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      run: pnpm install
+    - name: Build
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      run: pnpm build
+      env:
+        GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
+        SENTRY_DSN: ${{ secrets.SENTRY_DSN }}
+    - name: Publish
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      run: pnpm publish-from-github
+      env:
+        NPM_TOKEN: ${{ secrets.NPM_TOKEN_ELEVATED }}
+        GA_TRACKING_ID: ${{ secrets.GA_TRACKING_ID }}
+        SENTRY_DSN: ${{ secrets.SENTRY_DSN }}

.github/workflows/required-pr-label.yml

@@ -0,0 +1,26 @@
+name: Required PR Label
+on:
+  pull_request:
+    types: [opened, labeled, unlabeled, synchronize]
+jobs:
+  label:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check PR Labels
+        uses: actions/github-script@v6
+        with:
+          script: |
+            let missing = false;
+            const labels = context.payload.pull_request.labels.map(l => l.name);
+            if (labels.filter(l => l.startsWith('area:')).length === 0) {
+              console.error('::error::Missing label: Please add at least one "area" label.');
+              missing = true;
+            }
+            if (labels.filter(l => l.startsWith('semver:')).length !== 1) {
+              console.error('::error::Missing label: Please add exactly one "semver" label.');
+              missing = true;
+            }
+            if (missing) {
+              process.exit(1);
+            }
+            console.log('::notice::Success: This pull request has correct labels, thanks!');

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

@@ -0,0 +1,47 @@
+name: CLI
+
+on:
+  push:
+    branches:
+    - main
+    tags:
+    - '!*'
+  pull_request:
+
+env:
+  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:
+  test:
+    name: CLI
+    timeout-minutes: 40
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest]
+        node: [16]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          fetch-depth: 2
+      - uses: actions/setup-go@v3
+        with:
+          go-version: '1.18'
+      - uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node }}
+      - name: install pnpm@7.24.2
+        run: npm i -g pnpm@7.24.2
+      - run: pnpm install
+      - run: pnpm run build
+      - run: pnpm test-cli
+        env:
+          VERCEL_TEST_TOKEN: ${{ secrets.VERCEL_TEST_TOKEN }}
+          VERCEL_TEST_REGISTRATION_URL: ${{ secrets.VERCEL_TEST_REGISTRATION_URL }}

.github/workflows/test-unit.yml

@@ -0,0 +1,50 @@
+name: Unit
+
+on:
+  push:
+    branches:
+    - main
+    tags:
+    - '!*'
+  pull_request:
+
+env:
+  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:
+  test:
+    name: Unit
+    timeout-minutes: 20
+    strategy:
+      fail-fast: false
+      matrix:
+        os: [ubuntu-latest, macos-latest, windows-latest]
+        node: [16]
+    runs-on: ${{ matrix.os }}
+    steps:
+      - uses: actions/setup-go@v3
+        with:
+          go-version: '1.13.15'
+      - uses: actions/checkout@v3
+        with:
+            fetch-depth: 2
+      - uses: actions/setup-node@v3
+        with:
+            node-version: ${{ matrix.node }}
+      - name: install pnpm@7.24.2
+        run: npm i -g pnpm@7.24.2
+      - run: pnpm install
+      - run: pnpm run build
+      - run: pnpm run lint
+        if: matrix.os == 'ubuntu-latest' && matrix.node == 14 # only run lint once
+      - run: pnpm run test-unit
+      - run: pnpm -C packages/cli run coverage
+        if: matrix.os == 'ubuntu-latest' && matrix.node == 14 # only run coverage once
+        env:
+          CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}

.github/workflows/test.yml

@@ -0,0 +1,105 @@
+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-go@v3
+        with:
+          go-version: '1.13.15'
+      - uses: actions/setup-node@v3
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - name: install pnpm@7.24.2
+        run: npm i -g pnpm@7.24.2
+      - 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@ae34b392ef30297f2b672f9afb3c329bde9bd487
+        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-go@v3
+        with:
+          go-version: '1.13.15'
+      - uses: actions/setup-node@v3
+        with:
+          node-version: ${{ 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/
+
+      - name: install pnpm@7.24.2
+        run: npm i -g pnpm@7.24.2
+
+      - run: pnpm install
+
+      - name: Build ${{matrix.packageName}} and all its dependencies
+        run: node utils/gen.js && node_modules/.bin/turbo run build --cache-dir=".turbo" --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 --cache-dir=".turbo" --scope=${{matrix.packageName}} --no-deps -- ${{ join(matrix.testPaths, ' ') }}
+        shell: bash
+        env:
+          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'
+
+  conclusion:
+    needs:
+      - test
+    runs-on: ubuntu-latest
+    name: E2E
+    steps:
+      - name: Done
+        run: echo "Done."

.gitignore

@@ -1,9 +1,33 @@
-# dependencies
 node_modules
-
-# build output
 dist
-packed
-
-# logs
+.vscode
 npm-debug.log
+yarn-error.log
+.nyc_output
+coverage
+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
+test/lib/deployment/failed-page.txt
+.DS_Store
+.next
+/.env
+/public
+__pycache__
+.vercel
+.turbo
+.eslintcache
+turbo-cache-key.json

.husky/.gitignore

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

.husky/pre-commit

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

.kodiak.toml

@@ -0,0 +1,17 @@
+version = 1
+
+[merge]
+automerge_label = ["pr: automerge"]
+blacklist_title_regex = "^WIP.*"
+blacklist_labels = ["work in progress"]
+method = "squash"
+delete_branch_on_merge = true
+block_on_reviews_requested = false
+notify_on_conflict = true
+optimistic_updates = true
+
+[merge.message]
+title = "pull_request_title"
+body = "pull_request_body"
+include_pr_number = true
+body_type = "markdown"

.npmrc

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

.prettierignore

@@ -0,0 +1,9 @@
+# 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

.travis.yml

@@ -1,25 +0,0 @@
-{
-  "language": "node_js",
-  "node_js": [
-    "node"
-  ],
-  "before_script": [
-    "yarn run pack"
-  ],
-  "after_success": [
-    'yarn global add slackup',
-    './scripts/slack.js'
-  ],
-  "deploy": {
-    "provider": "releases",
-    "api_key": {
-      "secure": "ff5V20LO5B8nwguQYtmb3Es/WHBP6GYFo0yOaiw7d1GrmeVFyZauQ7CQgI41toEuYnPlDxd+CQACXjARKLGzJbz80bIPuHZ07GevrmhEgYVHq4DuWAiQnuVf0CJKehDUAKUtR+c8giMQK9tE7O+M+yBciiC9UEKYRCmfyQPXOnEU+cRWNaL0PH2hnlz1AIgScdLblAqdJbVUjHQ+eT2yYeKx2qR09pxu9MDwYLCfpWsLa+8PAcS4MHyuU7mqF27Y484Ab/X3kwNDhnzanyG9YhgHcCeNTZULDQUAJh7Pdf5uQvsfrcgNh1IzY+xvxmYPo2YavkGoDraPBqV46L7FP7KZX3pyh+crR1J+915pE96yHcV3+o40OgSuvW1jw7JCnVkkefryrABFlu7Dez7vd2mlUE+YXcnWhOEp12KUC2izfvm+hvQOqlA+I4VmCWHCA4peM93upQ3QCRhfB18L7JjoGo9/UvUF7wtm/1urMRSU3pWfcNRUtAg497gUUEbA9zVpLya+fQ2QdDe13L/03lYOz78NtDrzSIaWDfJTFrYSpgzwqmSwsTuismxP4NUV0aVEnpL9M+iKBxT0aLWeOIylGsnO5Ido7A+6SGqh8qqeNI84VRKZheOLV6GAqM5zvPDPeFdijRFNbP1n+rW+eepv2uCU8Km38FfhV1Qp85k="
-    },
-    "file_glob": true,
-    "file": "packed/*",
-    "skip_cleanup": true,
-    "on": {
-      "tags": true
-    }
-  }
-}

.vercelignore

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

.yarnrc

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

DEVELOPING_A_RUNTIME.md

@@ -0,0 +1,486 @@
+# 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.
+
+> 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.
+
+See the [Runtimes Documentation](https://vercel.com/docs/runtimes) to view example usage.
+
+## Runtime Exports
+
+### `version`
+
+A **required** exported constant that decides which version of the Runtime API to use.
+
+The latest and suggested version is `3`.
+
+**Example:**
+
+```typescript
+export const version = 3;
+```
+
+### `build()`
+
+A **required** exported function that returns a Serverless Function.
+
+> What's a Serverless Function? Read about [Serverless Functions](https://vercel.com/docs/concepts/functions/serverless-functions) to learn more.
+
+**Example:**
+
+```typescript
+import { BuildOptions, createLambda } from '@vercel/build-utils';
+
+export async function 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…
+    ],
+  };
+}
+```
+
+### `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.
+
+**Example:**
+
+```typescript
+import { PrepareCacheOptions } from '@vercel/build-utils';
+
+export async function prepareCache(options: PrepareCacheOptions) {
+  // Create a mapping of file names and `File` object instances to cache here…
+
+  return {
+    'path-to-file': File,
+  };
+}
+```
+
+### `shouldServe()`
+
+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.
+
+**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;
+}
+```
+
+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).
+
+### `startDevServer()`
+
+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.
+
+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.
+
+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.
+
+> **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 };
+}
+```
+
+### 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.
+
+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.
+
+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.
+
+The `analyze` step can modify that directory, and it will not be re-created when it's supplied to `build` and `prepareCache`.
+
+### Accessing Environment and Secrets
+
+The env and secrets specified by the user as `build.env` are passed to the Runtime process. This means you can access user env via `process.env` in Node.js.
+
+### 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`.
+
+## `@vercel/build-utils` Types
+
+### `Files`
+
+```typescript
+import { File } from '@vercel/build-utils';
+type Files = { [filePath: string]: File };
+```
+
+This is an abstract type that is implemented as a plain [JavaScript Object](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object). It's helpful to think of it as a virtual filesystem representation.
+
+When used as an input, the `Files` object will only contain `FileRefs`. When `Files` is an output, it may consist of `Lambda` (Serverless Functions) types as well as `FileRefs`.
+
+An example of a valid output `Files` object is:
+
+```javascript
+{
+  "index.html": FileRef,
+  "api/index.js": Lambda
+}
+```
+
+### `File`
+
+This is an abstract type that can be imported if you are using TypeScript.
+
+```typescript
+import { File } from '@vercel/build-utils';
+```
+
+Valid `File` types include:
+
+- [`FileRef`](#fileref)
+- [`FileFsRef`](#filefsref)
+- [`FileBlob`](#fileblob)
+
+### `FileRef`
+
+```typescript
+import { FileRef } from '@vercel/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`.
+
+**Properties:**
+
+- `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
+
+### `FileFsRef`
+
+```typescript
+import { FileFsRef } from '@vercel/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.
+
+**Properties:**
+
+- `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
+
+### `FileBlob`
+
+```typescript
+import { FileBlob } from '@vercel/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.
+
+**Properties:**
+
+- `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
+
+### `Lambda`
+
+```typescript
+import { Lambda } from '@vercel/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.
+
+**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
+
+### `LambdaRuntime`
+
+This is an abstract enumeration type that is implemented by one of the following possible `String` values:
+
+- `nodejs18.x`
+- `nodejs16.x`
+- `nodejs14.x`
+- `go1.x`
+- `java11`
+- `python3.9`
+- `dotnet6`
+- `dotnetcore3.1`
+- `ruby2.7`
+- `provided.al2`
+
+## `@vercel/build-utils` Helper Functions
+
+The following is exposed by `@vercel/build-utils` to simplify the process of writing Runtimes, manipulating the file system, using the above types, etc.
+
+### `createLambda()`
+
+Signature: `createLambda(Object spec): Lambda`
+
+```typescript
+import { createLambda } from '@vercel/build-utils';
+```
+
+Constructor for the [`Lambda`](#lambda) type.
+
+```js
+const { createLambda, FileBlob } = require('@vercel/build-utils');
+await createLambda({
+  runtime: 'nodejs8.10',
+  handler: 'index.main',
+  files: {
+    'index.js': new FileBlob({ data: 'exports.main = () => {}' }),
+  },
+});
+```
+
+### `download()`
+
+Signature: `download(): Files`
+
+```typescript
+import { download } from '@vercel/build-utils';
+```
+
+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_.
+
+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()`
+
+Signature: `glob(): Files`
+
+```typescript
+import { glob } from '@vercel/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).
+
+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');
+
+exports.build = ({ files, workPath }) => {
+  await download(files, workPath);
+  return glob('**', workPath);
+};
+```
+
+### `getWritableDirectory()`
+
+Signature: `getWritableDirectory(): String`
+
+```typescript
+import { getWritableDirectory } from '@vercel/build-utils';
+```
+
+In some occasions, you might want to write to a temporary directory.
+
+### `rename()`
+
+Signature: `rename(Files, Function): Files`
+
+```typescript
+import { rename } from '@vercel/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 originalFiles = { 'one.go': fileFsRef1, 'two.go': fileFsRef2 }
+const renamedFiles = rename(originalFiles, path => path.replace(/\.go$/, '')
+```

LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "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.
+
+      "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.
+
+      "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.
+
+      "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.
+
+      "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.
+
+   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.
+
+   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
+
+      (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
+
+      (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.
+
+   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.
+
+   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.
+
+   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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      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.
+
+   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.

README.md

@@ -0,0 +1,46 @@
+<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>
+</p>
+
+<p align="center">
+  Develop. Preview. Ship.
+</p>
+
+<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/>
+
+## Vercel
+
+Vercel is the platform for frontend developers, providing the speed and reliability innovators need to create at the moment of inspiration.
+
+We enable teams to iterate quickly and develop, preview, and ship delightful user experiences. Vercel has zero-configuration support for 35+ frontend frameworks and integrates with your headless content, commerce, or database of choice.
+
+## 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.
+
+## Documentation
+
+For details on how to use Vercel, check out our [documentation](https://vercel.com/docs).
+
+## Contributing
+
+This project uses [pnpm](https://pnpm.io/) to install dependencies and run scripts.
+
+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`.
+
+See the [Contributing Guidelines](./.github/CONTRIBUTING.md) for more details.
+
+## Reference
+
+- [Code of Conduct](./.github/CODE_OF_CONDUCT.md)
+- [Contributing Guidelines](./.github/CONTRIBUTING.md)
+- [Apache 2.0 License](./LICENSE)

api/_lib/examples/example-list.ts

@@ -0,0 +1,25 @@
+import Frameworks, { Framework } from '../../../packages/frameworks';
+
+interface Example {
+  example: string;
+  path: string;
+  demo: string;
+  description: string;
+  tagline: string;
+  framework: string;
+}
+
+export async function getExampleList(): Promise<Example[]> {
+  return (Frameworks as Framework[])
+    .filter(f => f.demo)
+    .map(framework => {
+      return {
+        example: framework.name,
+        path: `/${framework.slug}`,
+        demo: framework.demo,
+        description: framework.description,
+        tagline: framework.tagline,
+        framework: framework.slug,
+      };
+    });
+}

api/_lib/examples/extract.ts

@@ -0,0 +1,18 @@
+/**
+ * Download zip and extract to target directory
+ */
+
+import got from 'got';
+import unzip from 'unzip-stream';
+
+export async function extract(sourceUrl: string, targetPath: string) {
+  return new Promise((resolve, reject) => {
+    got
+      .stream(sourceUrl)
+      .pipe(unzip.Extract({ path: targetPath }))
+      .on('close', resolve)
+      .on('error', err => {
+        reject(new Error('Failed extracting from github.'));
+      });
+  });
+}

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

@@ -0,0 +1,73 @@
+import fetch from 'node-fetch';
+import { Repo } from '../types';
+import { getExampleList } from './example-list';
+
+/**
+ * Fetch the meta info of a public github repo
+ * @param {object} repo parsed by the `parse-github-url` package
+ */
+export async function getGitHubRepoInfo(repo: Repo) {
+  const response = await fetch(`https://api.github.com/repos/${repo.repo}`, {
+    headers: {
+      Accept: 'application/vnd.github.machine-man-preview+json',
+      // If we don't use a personal access token,
+      // it will get rate limited very easily.
+      Authorization: `Bearer ${process.env.GITHUB_ACCESS_TOKEN}`,
+    },
+  });
+
+  if (response.status !== 200) {
+    console.log(`Non-200 response code from GitHub: ${response.status}`);
+    console.log(await response.text());
+    return null;
+  }
+
+  const parsed = await response.json();
+
+  if (parsed.full_name !== repo.repo) {
+    console.log(`Invalid response from GitHub`);
+    console.log(`Received:`, parsed);
+    return null;
+  }
+
+  const data: { [key: string]: any } = {
+    id: parsed.full_name,
+    name: parsed.name,
+    url: parsed.html_url,
+    owner: parsed.owner.login,
+    description: parsed.description,
+    homepage: parsed.homepage,
+    size: parsed.size,
+    createdAt: parsed.created_at,
+    updatedAt: parsed.updated_at,
+    stars: parsed.stargazers_count,
+    branch: repo.branch,
+  };
+
+  const subdirPath = repo.repo + '/tree/' + repo.branch + '/';
+
+  if (repo.path.startsWith(subdirPath)) {
+    // subdir
+    data.subdir = repo.path.slice(subdirPath.length).split('/');
+  }
+
+  if (data.id === 'vercel/vercel' && data.subdir && data.subdir[0] === 'examples') {
+
+    // from our examples, add `homepage` and `description` fields
+    const example = data.subdir[1];
+    const exampleList = await getExampleList();
+
+    for (const item of exampleList) {
+      if (item.path === `/${example}`) {
+        data.homepage = item.demo;
+        data.description = item.description;
+        data.exampleName = item.example;
+        data.tagline = item.tagline;
+        data.framework = item.framework;
+        return data;
+      }
+    }
+  }
+
+  return data;
+}

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

@@ -0,0 +1,45 @@
+import fetch from 'node-fetch';
+
+interface Repo {
+  repo: string;
+  owner: {
+    username: string;
+  };
+  username: string;
+  branch: string;
+}
+
+/**
+ * Fetch the meta info of a public gitlab repo
+ * @param {object} repo parsed by the `parse-github-url` package
+ */
+export async function getGitLabRepoInfo(repo: Repo) {
+  const response = await fetch(
+    `https://gitlab.com/api/v4/projects/${encodeURIComponent(repo.repo)}`
+  );
+
+  if (response.status !== 200) {
+    console.log(`Non-200 response code from GitLab: ${response.status}`);
+    return null;
+  }
+
+  const parsed = await response.json();
+  if (parsed.path_with_namespace !== repo.repo) {
+    console.log(`Invalid response from GitLab`);
+    return null;
+  }
+
+  return {
+    id: parsed.path_with_namespace,
+    name: parsed.path,
+    url: parsed.web_url,
+    owner: parsed.owner ? parsed.owner.username : repo.owner,
+    description: parsed.description,
+    homepage: null,
+    size: 0,
+    createdAt: parsed.created_at,
+    updatedAt: parsed.last_activity_at,
+    stars: parsed.star_count,
+    branch: repo.branch,
+  };
+}

api/_lib/examples/map-old-to-new.ts

@@ -0,0 +1,28 @@
+export const mapOldToNew: { [key: string]: string[] } = {
+  'go-image-to-ascii': ['vanilla-functions'],
+  markdown: ['hexo', 'docusaurus', 'docz', 'jekyll'],
+  'mdx-deck': ['docz'],
+  'mdx-deck-advanced': ['docz'],
+  'nextjs-mysql': ['nextjs'],
+  'nextjs-news': ['nextjs'],
+  'nextjs-nodejs-mongodb': ['nextjs'],
+  'nextjs-static': ['nextjs'],
+  'node-server': ['svelte-functions'],
+  nodejs: ['svelte-functions'],
+  'nodejs-canvas-partyparrot': ['svelte-functions'],
+  'nodejs-coffee': ['svelte-functions'],
+  'nodejs-hapi': ['svelte-functions'],
+  'nodejs-koa': ['svelte-functions'],
+  'nodejs-koa-ts': ['gatsby-functions'],
+  'nodejs-micro': ['svelte-functions'],
+  'nodejs-ms-graph-security-api': ['svelte-functions'],
+  'nodejs-pdfkit': ['svelte-functions'],
+  'nodejs-ts': ['gatsby-functions'],
+  'nuxt-static': ['nuxtjs'],
+  static: ['vanilla'],
+  typescript: ['gatsby-functions'],
+  umi: ['umijs'],
+  'vanilla-go': ['vanilla-functions'],
+  'vanilla-json-api': ['svelte-functions'],
+  'vue-ssr': ['vue'],
+};

api/_lib/examples/summary.ts

@@ -0,0 +1,20 @@
+/**
+ * Get example list from extracted folder
+ */
+
+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[] {
+  if (!exists(source) || !isDirectory(source)) {
+    return [];
+  }
+
+  return readdirSync(source, { withFileTypes: true })
+    .filter(d => !isDotFile(d.name))
+    .filter(d => d.isDirectory())
+    .map(d => d.name);
+}

api/_lib/script/build.ts

@@ -0,0 +1,88 @@
+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())
+    .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/types.ts

@@ -0,0 +1,9 @@
+export interface Repo {
+  repo: string;
+  owner: {
+    username: string;
+  };
+  username: string;
+  branch: string;
+  path: string;
+}

api/_lib/util/assert-env.ts

@@ -0,0 +1,9 @@
+export function assertEnv(name: string) {
+  const value = process.env[name];
+
+  if (!value) {
+    throw new Error(`Missing env "${name}"`);
+  }
+
+  return value;
+}

api/_lib/util/error-handler.ts

@@ -0,0 +1,45 @@
+import { init, captureException, withScope } from '@sentry/node';
+import { assertEnv } from './assert-env';
+
+const serviceName = 'api-frameworks';
+
+let sentryInitDone = false;
+
+function initSentry() {
+  if (sentryInitDone) {
+    return;
+  }
+
+  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}`,
+  });
+}
+
+export function errorHandler(error: Error, extras?: { [key: string]: any }) {
+  if (!process.env.SENTRY_DSN) {
+    return;
+  }
+
+  initSentry();
+
+  try {
+    withScope(scope => {
+      scope.setTag('service', serviceName);
+      scope.setTag('function_name', assertEnv('AWS_LAMBDA_FUNCTION_NAME'));
+
+      for (const [k, v] of Object.entries(extras)) {
+        scope.setExtra(k, v);
+      }
+
+      captureException(error);
+    });
+  } catch (e) {
+    console.error(`Failed to report error to Sentry: ${e}`);
+  }
+}

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

@@ -0,0 +1,44 @@
+import { VercelRequest, VercelResponse } from '@vercel/node';
+import { errorHandler } from './error-handler';
+
+type Handler = (req: VercelRequest, res: VercelResponse) => Promise<any>;
+
+export function withApiHandler(handler: Handler): Handler {
+  return async (req: VercelRequest, res: VercelResponse) => {
+    res.setHeader('Access-Control-Allow-Origin', '*');
+    res.setHeader('Access-Control-Allow-Methods', 'GET');
+    res.setHeader(
+      'Access-Control-Allow-Headers',
+      'Authorization, Accept, Content-Type'
+    );
+
+    if (req.method === 'OPTIONS') {
+      return res.status(200).json({});
+    }
+
+    if (req.method !== 'GET') {
+      return res.status(405).json({
+        error: {
+          code: 'method_not_allowed',
+          message: 'Only GET requests are supported for this endpoint.',
+        },
+      });
+    }
+
+    try {
+      const result = await handler(req, res);
+      return result;
+    } catch (error) {
+      errorHandler(error, {
+        url: req.url,
+      });
+
+      return res.status(500).json({
+        error: {
+          code: 'unexpected_error',
+          message: 'An unexpected error occurred.',
+        },
+      });
+    }
+  };
+}

api/examples/download/[segment].ts

@@ -0,0 +1,60 @@
+import fs from 'fs';
+// @ts-ignore
+import tar from 'tar-fs';
+import { extract } from '../../_lib/examples/extract';
+import { VercelRequest, VercelResponse } from '@vercel/node';
+import { withApiHandler } from '../../_lib/util/with-api-handler';
+
+const TMP_DIR = '/tmp';
+
+function isDirectory(path: string) {
+  return fs.existsSync(path) && fs.lstatSync(path).isDirectory();
+}
+
+function notFound(res: VercelResponse, message: string) {
+  return res.status(404).send({
+    error: {
+      code: 'not_found',
+      message,
+    },
+  });
+}
+
+function streamToBuffer(stream: any) {
+  return new Promise((resolve, reject) => {
+    const buffers: any[] = [];
+    stream.on('error', (err: any) => {
+      reject(err);
+    });
+    stream.on('data', (b: any) => {
+      buffers.push(b);
+    });
+    stream.on('end', () => {
+      resolve(Buffer.concat(buffers));
+    });
+  });
+}
+
+export default withApiHandler(async function (
+  req: VercelRequest,
+  res: VercelResponse
+) {
+  const ext = '.tar.gz';
+  const { segment = '' } = req.query;
+
+  if (Array.isArray(segment) || !segment.endsWith(ext)) {
+    return notFound(res, `Missing ${ext} suffix.`);
+  }
+
+  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}`;
+
+  if (!isDirectory(directory)) {
+    return notFound(res, `Example '${example}' was not found.`);
+  }
+
+  const stream = tar.pack(directory);
+  return res.send(await streamToBuffer(stream));
+});

api/examples/info.ts

@@ -0,0 +1,44 @@
+// A proxy to get the basic info of an existing github/gitlab repo:
+// GET /info?repo=vercel/micro
+
+// @ts-ignore
+import parseGitUrl from 'parse-github-url';
+import { VercelRequest, VercelResponse } from '@vercel/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
+) {
+  const repoPath = decodeURIComponent((req.query.repo as string) || '');
+
+  if (!repoPath) {
+    return res.status(404).json({
+      error: {
+        code: 'not_found',
+        message: 'Please provide the `repo` parameter.',
+      },
+    });
+  }
+
+  const repo = parseGitUrl(repoPath);
+
+  if (!repo.repo) {
+    return res.status(400).json({
+      error: {
+        code: 'invalid_repo_url',
+        message: 'Repository URL is invalid.',
+      },
+    });
+  }
+
+  if (repo.host === 'github.com') {
+    // URL is 'https://github.com/user/repo' or 'user/repo'
+    return res.json((await getGitHubRepoInfo(repo)) || {});
+  }
+
+  // gitlab
+  res.json((await getGitLabRepoInfo(repo)) || {});
+});

api/frameworks.ts

@@ -0,0 +1,33 @@
+import { VercelRequest, VercelResponse } from '@vercel/node';
+import { withApiHandler } from './_lib/util/with-api-handler';
+import _frameworks, { 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,
+    };
+
+    return framework;
+  });
+
+export default withApiHandler(async function (
+  req: VercelRequest,
+  res: VercelResponse
+) {
+  res.setHeader('Access-Control-Allow-Origin', '*');
+  res.setHeader('Access-Control-Allow-Methods', 'GET');
+  res.setHeader(
+    'Access-Control-Allow-Headers',
+    'Authorization, Accept, Content-Type'
+  );
+  return res.status(200).json(frameworks);
+});

api/package.json

@@ -0,0 +1,22 @@
+{
+  "name": "api",
+  "private": true,
+  "version": "0.0.0",
+  "description": "API for the vercel/vercel repo",
+  "main": "index.js",
+  "scripts": {},
+  "dependencies": {
+    "@sentry/node": "5.11.1",
+    "got": "10.2.1",
+    "node-fetch": "2.6.7",
+    "parse-github-url": "1.0.2",
+    "tar-fs": "2.0.0",
+    "unzip-stream": "0.3.0"
+  },
+  "devDependencies": {
+    "@types/node": "16.18.11",
+    "@types/node-fetch": "2.5.4",
+    "@vercel/node": "*",
+    "typescript": "4.3.4"
+  }
+}

api/tsconfig.json

@@ -0,0 +1,16 @@
+{
+  "compilerOptions": {
+    "target": "ES2020",
+    "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"]
+}

codecov.yml

@@ -0,0 +1,10 @@
+codecov:
+  require_ci_to_pass: yes
+
+coverage:
+  status:
+    project: off
+    patch: off
+
+fixes:
+  - "::packages/cli/"         # move root   e.g., "path/" => "after/path/"

download/install.js

@@ -1,16 +0,0 @@
-/* eslint-disable no-var */
-
-// Native
-var path = require('path')
-var fs = require('fs')
-
-var dist = path.join(__dirname, 'dist')
-var src = path.join(__dirname, 'src')
-
-// Don't install when developing locally
-if (fs.existsSync(src)) {
-  // eslint-disable-next-line unicorn/no-process-exit
-  process.exit(0)
-}
-
-require(path.join(dist, 'download.js'))

download/src/chmod.js

@@ -1,10 +0,0 @@
-// Native
-import fs from 'fs'
-
-export default function (file) {
-  const s = fs.statSync(file)
-  const newMode = s.mode | 64 | 8 | 1
-  if (s.mode === newMode) return
-  const base8 = newMode.toString(8).slice(-3)
-  fs.chmodSync(file, base8)
-}

download/src/index.js

@@ -1,184 +0,0 @@
-/* eslint-disable unicorn/no-process-exit */
-
-// Native
-import fs from 'fs'
-import path from 'path'
-import { spawnSync } from 'child_process'
-import zlib from 'zlib'
-
-// Packages
-import onDeath from 'death'
-import fetch from 'node-fetch'
-import retry from 'async-retry'
-import which from 'which-promise'
-
-// Utilities
-import plusxSync from './chmod'
-import {
-  disableProgress,
-  enableProgress,
-  info,
-  showProgress,
-  warn
-} from './log'
-
-fetch.Promise = Promise
-global.Promise = Promise
-let { platform } = process
-if (detectAlpine()) platform = 'alpine'
-
-const packagePath = path.join(__dirname, '../../package.json')
-const packageJSON = JSON.parse(fs.readFileSync(packagePath, 'utf8'))
-
-const now = path.join(__dirname, 'now')
-const targetWin32 = path.join(__dirname, 'now.exe')
-const target = platform === 'win32' ? targetWin32 : now
-const partial = target + '.partial'
-const backup = target + '.' + packageJSON.version + '.backup'
-
-const platformToName = {
-  alpine: 'now-alpine',
-  darwin: 'now-macos',
-  linux: 'now-linux',
-  win32: 'now-win.exe'
-}
-
-function detectAlpine () {
-  if (platform !== 'linux') return false
-  // https://github.com/sass/node-sass/issues/1589#issuecomment-265292579
-  const ldd = spawnSync('ldd', [ process.execPath ]).stdout.toString()
-  return /\bmusl\b/.test(ldd)
-}
-
-async function download() {
-  try {
-    fs.writeFileSync(
-      now,
-      '#!/usr/bin/env node\n' +
-        'console.log("Please wait until the \'now\' installation completes!")\n'
-    )
-  } catch (err) {
-    if (err.code === 'EACCES') {
-      warn(
-        'Please try installing now CLI again with the `--unsafe-perm` option.'
-      )
-      info('Example: `npm i -g --unsafe-perm now`')
-
-      process.exit()
-    }
-
-    throw err
-  }
-
-  onDeath(() => {
-    fs.writeFileSync(
-      now,
-      '#!/usr/bin/env node\n' +
-        'console.log("The \'now\' installation did not complete successfully.")\n' +
-        'console.log("Please run \'npm i -g now\' to reinstall!")\n'
-    )
-    process.exit()
-  })
-
-  info('For the source code, check out: https://github.com/zeit/now-cli')
-
-  // Print an empty line
-  console.log('')
-
-  await retry(async () => {
-    enableProgress('Downloading now CLI ' + packageJSON.version)
-    showProgress(0)
-
-    try {
-      const name = platformToName[platform]
-      const url = `https://cdn.zeit.co/releases/now-cli/${packageJSON.version}/${name}`
-      const resp = await fetch(url, { compress: false })
-
-      if (resp.status !== 200) {
-        throw new Error(resp.statusText + ' ' + url)
-      }
-
-      const size = resp.headers.get('content-length')
-
-      if (!size) {
-        throw new Error('Not found (content-length is absent)')
-      }
-
-      const ws = fs.createWriteStream(partial)
-
-      await new Promise((resolve, reject) => {
-        let bytesRead = 0
-
-        resp.body
-          .on('error', reject)
-          .on('data', chunk => {
-            bytesRead += chunk.length
-            showProgress(100 * bytesRead / size)
-          })
-
-        const gunzip = zlib.createGunzip()
-
-        gunzip
-          .on('error', reject)
-
-        resp.body.pipe(gunzip).pipe(ws)
-
-        ws
-          .on('error', reject)
-          .on('close', () => {
-            showProgress(100)
-            resolve()
-          })
-      })
-    } finally {
-      disableProgress()
-    }
-  }, {
-    retries: 500,
-    onRetry: (err) => console.error(err)
-  })
-
-  fs.renameSync(partial, target)
-  fs.writeFileSync(backup, fs.readFileSync(target))
-}
-
-async function main() {
-  if (fs.existsSync(backup)) {
-    fs.writeFileSync(target, fs.readFileSync(backup))
-  } else {
-    await download()
-  }
-
-  if (platform === 'win32') {
-    // Now.exe is executed only
-    fs.unlinkSync(now)
-    try {
-      // Workaround for https://github.com/npm/cmd-shim/pull/25
-      const globalPath = path.dirname(await which('npm'))
-      const gitBashFile = path.join(globalPath, 'now')
-      fs.writeFileSync(
-        gitBashFile,
-        '#!/bin/sh\n' +
-          'basedir=$(dirname "$(echo "$0" | sed -e \'s,\\\\,/,g\')")\n' +
-          '\n' +
-          'case `uname` in\n' +
-          '    *CYGWIN*) basedir=`cygpath -w "$basedir"`;;\n' +
-          'esac\n' +
-          '\n' +
-          fs.readFileSync(gitBashFile, 'utf8')
-      )
-    } catch (err) {
-      if (err.code !== 'ENOENT') {
-        // Not a problem. only git cmd will not work
-        console.error(err)
-      }
-    }
-  } else {
-    plusxSync(now)
-  }
-}
-
-main().catch(err => {
-  console.error(err)
-  process.exit(2)
-})

download/src/log.js

@@ -1,43 +0,0 @@
-// Packages
-import assert from 'assert'
-import chalk from 'chalk'
-import Progress from 'progress'
-
-let bar
-
-export function enableProgress(text) {
-  assert(!bar)
-
-  bar = new Progress(`> ${text} [:bar] :percent`, {
-    stream: process.stdout,
-    width: 20,
-    complete: '=',
-    incomplete: ' ',
-    total: 100
-  })
-}
-
-export function info(text) {
-  console.log(`> ${text}`)
-}
-
-export function warn(text) {
-  console.log(chalk.red('> Warning!'), text)
-}
-
-export function showProgress(percentage) {
-  assert(bar)
-  bar.update(percentage / 100)
-}
-
-export function disableProgress() {
-  assert(bar)
-
-  // It is auto-completed once it updates to 100
-  // otherwise it outputs a blank line
-  if (!bar.complete) {
-    bar.terminate()
-  }
-
-  bar = undefined
-}

download/webpack.config.js

@@ -1,34 +0,0 @@
-// Native
-const path = require('path')
-
-module.exports = {
-  target: 'node',
-  node: {
-    __dirname: false,
-    __filename: false,
-    process: false
-  },
-  entry: [
-    './src/index.js'
-  ],
-  output: {
-    path: path.join(__dirname, 'dist'),
-    filename: 'download.js'
-  },
-  module: {
-    loaders: [ {
-      test: /.js$/,
-      loader: 'babel-loader',
-      exclude: /node_modules/,
-      query: {
-        plugins: [
-          'transform-async-to-generator',
-          'transform-runtime'
-        ],
-        presets: [
-          'es2015'
-        ]
-      }
-    } ]
-  }
-}

errors/cant-solve-challenge.md

@@ -0,0 +1,27 @@
+# The DNS Challenge Could Not Be Solved
+
+## Why This Error Occurred
+
+When generating a certificate, we have to prove ownership over the domain
+for the Certificate Authority (CA) that issues it. This error means that
+the provider couldn’t solve the requested challenges.
+
+## How to Fix It
+
+If your domain is pointing to Vercel DNS and you’re getting this error,
+it could be that:
+
+- The domain was acquired recently, and it might not be ready for use yet.
+- Required DNS records have not propagated yet.
+
+When running into this, ensure that your nameservers are configured correctly. Also, if you bought the domain recently or have made changes, please be patient,
+it might take a while for these to be ready.
+
+If your domain is _not_ pointing to Vercel DNS and you’re getting this
+error, the following methods could help:
+
+- When solving challenges _manually_, ensure that the TXT
+  records required to solve the challenges exist and are propagated. You can do so by querying the nameservers with `nslookup -q=TXT _acme-challenge.domain.com` depending on the Common Names you want for your certificate.
+
+- If you are not solving the challenges manually you must ensure that you have an
+  `ALIAS` and `CNAME` records in place. Ensure also that you have disabled automatic redirects to `https` and ensure all changes were propagated.

errors/deploy-invalid-dc.md

@@ -0,0 +1,37 @@
+# Invalid Region or DC Identifier
+
+#### Why This Error Occurred
+
+When supplying `regions` configuration, you
+used an unknown or invalid DC identifier.
+
+#### Possible Ways to Fix It
+
+Check your `vercel.json` or `--regions` flag and
+make sure you are using a valid string. 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 Vercel CLI, they currently are transformed to
+DC identifiers before being sent to our APIs.
+
+**Valid DC identifiers**:
+
+- `sfo1`
+- `bru1`
+- `gru1`
+- `iad1`
+
+When passing multiple `--regions` as a CLI parameter,
+make sure they're separated by a comma (`,`). For example:
+
+```console
+vercel --regions sfo,bru,gru
+```

errors/deployment-error.md

@@ -0,0 +1,13 @@
+# 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/dns-configuration-error.md

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

errors/domain-verification.md

@@ -0,0 +1,19 @@
+# Domain Verification
+
+#### Why This Error Occurred
+
+The domain you supplied cannot be verified using the intended nameservers.
+
+#### Possible Way to Fix It
+
+Apply the intended set of nameservers to your domain.
+
+You can retrieve both the intended nameservers and TXT verification record for the domain you wish to verify by running `vercel domains inspect <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>`.
+
+#### Resources
+
+- [Vercel Custom Domains Documentation](https://vercel.com/docs/concepts/projects/custom-domains)

errors/env-no-secret.md

@@ -0,0 +1,17 @@
+# Secret Not Found
+
+#### Why This Error Occurred
+
+You specified the `--env` or `-e` flag with the value of a secret. However, the secret doesn't exist in the current scope you're in.
+
+#### Possible Ways to Fix It
+
+Make sure to specify the environment variable and secret like that:
+
+```bash
+vercel -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.

errors/env-value-invalid-type.md

@@ -0,0 +1,21 @@
+# Bad Type in Env Value
+
+#### Why This Error Occurred
+
+You supplied a value in the `env` of your deployment whose type is not allowed.
+
+This occurs for example if you use a `Boolean` as a type:
+
+```json
+{
+  "env": {
+    "VALID": 1,
+    "INVALID": true
+  }
+}
+```
+
+#### Possible Ways to Fix It
+
+The only accepted types are `String` or `Number`. If you're using a
+`Boolean`, consider using `1` (`Number`) or `"true"` (`String`).

errors/invalid-route-source.md

@@ -0,0 +1,53 @@
+# Invalid Custom Route `source`
+
+#### Why This Error Occurred
+
+When defining custom routes a route was added that causes an error during parsing. This can be due to trying to use normal `RegExp` syntax like negative lookaheads (`?!exclude`) without following `path-to-regexp`'s syntax for it.
+
+#### Possible Ways to Fix It
+
+Wrap the `RegExp` part of your `source` as an un-named parameter.
+
+**Before**
+
+```js
+{
+  source: '/feedback/(?!general)',
+  destination: '/api/feedback/general'
+}
+```
+
+**After**
+
+```js
+{
+  source: '/feedback/((?!general).*)',
+  destination: '/api/feedback/general'
+}
+```
+
+Ensure any segments used in the `destination` property are also used in the `source` property.
+
+**Before**
+
+```js
+{
+  source: '/feedback/:type',
+  destination: '/api/feedback/:id'
+}
+```
+
+**After**
+
+```js
+{
+  source: '/feedback/:id',
+  destination: '/api/feedback/:id'
+}
+```
+
+### Useful Links
+
+- [path-to-regexp](https://github.com/pillarjs/path-to-regexp/tree/v6.1.0)
+- [named parameters](https://github.com/pillarjs/path-to-regexp/blob/v6.1.0/Readme.md#named-parameters)
+- [un-named paramters](https://github.com/pillarjs/path-to-regexp/blob/v6.1.0/Readme.md#unnamed-parameters)

errors/invalid-token-value.md

@@ -0,0 +1,11 @@
+# Invalid Token Value
+
+#### Why This Error Occurred
+
+The `--token` flag was specified, but its contents are invalid.
+
+#### Possible Ways to Fix It
+
+The `--token` flag must only contain numbers (0-9) and letters from the alphabet (a-z and A-Z). This needs to be the token of the user account as which you'd like to act.
+
+You can either get the token from the `./vercel/auth.json` file located in your user directory or [from the dashboard](https://vercel.com/account/tokens).

errors/missing-env-file.md

@@ -0,0 +1,27 @@
+# Missing Environment Variables While Developing
+
+#### 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).
+
+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`.
+
+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.
+
+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`.
+
+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`, then the `.env` file should look like this:
+
+```
+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).

errors/missing-env-key-value.md

@@ -0,0 +1,19 @@
+# Missing Env Key and Value
+
+#### Why This Error Occurred
+
+You specified the `--env` or `-e` flag and didn't add a name and value for the environment variable.
+
+#### Possible Ways to Fix It
+
+Make sure to set the name and value of the variable like this:
+
+```bash
+vercel -e VARIABLE_NAME="VALUE"
+```
+
+You can also specify a environment variable that contains a secret:
+
+```bash
+vercel -e VARIABLE_NAME=@secret-name
+```

errors/missing-scope-value.md

@@ -0,0 +1,11 @@
+# Missing Scope Value
+
+#### Why This Error Occurred
+
+The `--scope` flag was specified, but there's no value for it available.
+
+#### Possible Ways to Fix It
+
+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`.

errors/missing-token-value.md

@@ -0,0 +1,11 @@
+# Missing Token Value
+
+#### Why This Error Occurred
+
+The `--token` flag was specified, but there's no value for it available.
+
+#### Possible Ways to Fix It
+
+In order to make it work, you need to specify a value for the `--token` flag. This needs to be the token of the user account as which you'd like to act.
+
+You can either get the token from the `./vercel/auth.json` file located in your user directory or [from the dashboard](https://vercel.com/account/tokens).

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

@@ -0,0 +1,14 @@
+# `@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

@@ -0,0 +1,16 @@
+# `@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

@@ -0,0 +1,10 @@
+# No Credentials Found
+
+#### 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.
+
+#### 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

errors/no-open-port-found.md

@@ -0,0 +1,10 @@
+# No Open Port Found
+
+#### Why This Error Occurred
+
+Your application code exited or timed out before binding to a port number.
+
+#### Possible Ways to Fix It
+
+- For Node.js deployments, a call to [`Server#listen()`](https://nodejs.org/dist/latest/docs/api/http.html#http_server_listen) might be missing.
+- For Docker deployments, there might be a mismatch from what the `EXPOSE` directive specifies compared to what your application binds to.

errors/no-single-file-deployments.md

@@ -0,0 +1,9 @@
+# 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

@@ -0,0 +1,11 @@
+# No Token Allowed
+
+#### 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.
+
+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).
+
+#### 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.

errors/now-dev-as-dev-script.md

@@ -0,0 +1,9 @@
+# `vercel 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.
+
+#### Possible Ways to Fix It
+
+Adjust the `dev` script inside the `package.json` file to match what your framework uses to begin development mode, e.g. `next` for Next.js or `gatsby develop` for Gatsby.

errors/now-next-legacy-mode.md

@@ -0,0 +1,72 @@
+# `@vercel/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.
+
+The differences:
+
+Legacy:
+
+- Minimal lambda size of `2.2Mb` (approximately)
+- Forces `next@v7.0.2-canary.49` and `next-server@v7.0.2-canary.49`
+- Forces all `dependencies` to be `devDependencies`
+- Loads `next.config.js` on bootup, breaking sometimes when users didn't use `phases` to load files
+- Used `next-server` which is the full Next.js server with routing etc.
+- Runs `npm install`
+- Runs `npm run now-build`
+- Runs `npm install --production` after build
+
+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)
+- 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))
+- 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
+
+#### Possible Ways to Fix It
+
+In order to create the smallest possible lambdas Next.js has to be configured to build for the `serverless` target.
+
+1. Serverless Next.js requires Next.js 8 or later, to upgrade you can install the `latest` version:
+
+```
+npm install next --save
+```
+
+2. Add the `now-build` script to your `package.json`
+
+```json
+{
+  "scripts": {
+    "now-build": "next build"
+  }
+}
+```
+
+3. Add `target: 'serverless'` to `next.config.js`
+
+```js
+module.exports = {
+  target: 'serverless',
+  // Other options are still valid
+};
+```
+
+4. Optionally make sure the `"src"` in `"builds"` points to your application `package.json`
+
+```js
+{
+  "version": 2,
+  "builds": [{ "src": "package.json", "use": "@vercel/next" }]
+}
+```
+
+### Useful Links
+
+- [Serverless target implementation](https://github.com/vercel/now-builders/pull/150)

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

@@ -0,0 +1,49 @@
+# `@vercel/next` No Serverless Pages Built
+
+#### Why This Error Occurred
+
+This error occurs when your application is not configured for Serverless Next.js build output.
+
+#### Possible Ways to Fix It
+
+In order to create the smallest possible lambdas Next.js has to be configured to build for the `serverless` target.
+
+1. Serverless Next.js requires Next.js 8 or later, to upgrade you can install the `latest` version:
+
+```
+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]
+
+```json
+{
+  "scripts": {
+    "now-build": "next build"
+  }
+}
+```
+
+4. Add `target: 'serverless'` to `next.config.js` [deprecated]
+
+```js
+module.exports = {
+  target: 'serverless',
+  // Other options
+};
+```
+
+5. Remove `distDir` from `next.config.js` as `@vercel/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`
+
+```js
+{
+  "version": 2,
+  "builds": [{ "src": "package.json", "use": "@vercel/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

@@ -0,0 +1,16 @@
+# Routes Manifest Could Not Be Found
+
+#### Why This Error Occurred
+
+This error is often caused by a misconfigured "Build Command" or "Output Directory" 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":
+
+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.

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

@@ -0,0 +1,36 @@
+# `@vercel/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
+`package.json` file.
+
+In order for `vercel 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
+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`
+(port) option to bind to the `$PORT` specified from the builder:
+
+> _In Windows environments, reference the `PORT` environment variable with `%PORT%`_
+
+```
+{
+  ...
+  "scripts": {
+    ...
+    "dev": "gatsby develop -p $PORT"
+  }
+}
+```
+
+Consult your static builder program's `--help` or documentation to figure out what
+the command line flag to bind to a specific port is (in many cases, it is one of:
+`-p` / `-P` / `--port`).

errors/path-not-deployable.md

@@ -0,0 +1,15 @@
+# Path Not Deployable
+
+#### 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>`.
+
+#### Possible Ways to Fix It
+
+Make sure that you're not trying to deploy one of these directories:
+
+- User
+- Downloads
+- Desktop
+
+These directories are not supported for security reasons.

errors/scope-not-accessible.md

@@ -0,0 +1,11 @@
+# Scope Not Accessible
+
+#### Why This Error Occurred
+
+You specified the `--scope` flag and specified the ID or slug of a team that you're not a part of or a user whose account you don't own. This problem could also occur if your user credentials aren't valid anymore.
+
+#### 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.

errors/scope-not-existent.md

@@ -0,0 +1,11 @@
+# Scope Not Existent
+
+#### 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.
+
+#### 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.

errors/solve-challenges-manually.md

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

errors/unauthorized-domain.md

@@ -0,0 +1,9 @@
+# Not authorized to access domain
+
+#### Why This Error Occurred
+
+You tried to add or update a domain's configuration, but you don't have permission to modify the domain.
+
+#### 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.

examples/README.md

@@ -0,0 +1,39 @@
+# 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:
+
+```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>
+```
+
+Deploying your project can be done with **a single command**:
+
+```sh
+vercel                         # Deploy your project with the CLI
+```
+
+With the `vercel` command, your project will be built and served by Vercel, providing you with a URL that can be shared immediately.
+
+## 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.
+
+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.
+
+## Reporting Issues
+
+We actively encourage our community to raise issues and provide feedback on areas of 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.
+
+## 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.
+
+[![Join the community on GitHub Discussions](https://badgen.net/badge/join%20the%20discussion/on%20github/black?icon=github)](https://github.com/vercel/vercel/discussions)

examples/__tests__/integration/angular.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/astro.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/blitzjs.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/brunch.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

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

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

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

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/docusaurus.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/dojo.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/eleventy.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/ember.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/gatsby.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/gridsome.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/hexo.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/hugo.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/hydrogen.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/ionic-angular.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+  

examples/__tests__/integration/ionic-react.test.ts

@@ -0,0 +1,5 @@
+import { deployExample } from '../test-utils';
+it('should deploy', async () => {
+  await deployExample(__filename);
+});
+