Fix install command

.changeset/README.md

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

.changeset/config.json

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

.eslintignore

@@ -10,7 +10,6 @@ packages/*/test/fixtures
 packages/cli/@types
 packages/cli/download
 packages/cli/dist
-packages/cli/test/fixtures
 packages/cli/test/dev/fixtures
 packages/cli/bin
 packages/cli/link
@@ -27,6 +26,12 @@ packages/hydrogen/edge-entry.js
 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
 
@@ -39,7 +44,7 @@ packages/static-build/test/cache-fixtures
 packages/redwood/test/fixtures
 
 # remix
-packages/remix/test/fixtures-*
+packages/remix/test/fixtures
 
 # gatsby-plugin-vercel-analytics
 packages/gatsby-plugin-vercel-analytics

.github/CODEOWNERS

@@ -1,18 +1,16 @@
 # Documentation
 # https://help.github.com/en/articles/about-code-owners
 
-# Restricted Paths
-*                                        @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads
-/.github/workflows                       @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @ijjk
-/packages/fs-detectors                   @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @agadzik @chloetedder
-/packages/next                           @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @timneutkens @ijjk @ztanner @huozhi @Ethan-Arrowood
-/packages/routing-utils                  @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @ijjk
-/packages/static-build                   @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads
-/packages/edge                           @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @vercel/compute
-/examples                                @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @leerob
-/examples/create-react-app               @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @Timer
-/examples/nextjs                         @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @timneutkens @ijjk @ztanner @huozhi @Ethan-Arrowood
-/packages/node                           @TooTallNate @EndangeredMassa @trek @onsclom @jeffsee55 @erikareads @Kikobeats
-
-# Unrestricted Paths
-.changeset/
+*                                        @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/CONTRIBUTING.md

@@ -1,3 +1,109 @@
-## Contributing
+# Contributing
 
-See the [Contributing Guidelines](../README.md#contributing) for more details.
+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/DISCUSSION_TEMPLATE/general.yml

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

.github/DISCUSSION_TEMPLATE/help.yml

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

.github/DISCUSSION_TEMPLATE/ideas.yml

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

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

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

.github/ISSUE_TEMPLATE/config.yml

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

.github/dependabot.yml

@@ -1,302 +0,0 @@
-version: 2
-
-updates:
-  - directory: /packages/static-build/test/fixtures/angular-v17
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: '@angular*'
-    ignore:
-      - dependency-name: '@angular*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - '@angular*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/astro-v4
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'astro*'
-    ignore:
-      - dependency-name: 'astro*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'astro*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/hydrogen-v2023
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: '@remix-run*'
-      - dependency-name: '@shopify*'
-    ignore:
-      - dependency-name: '@remix-run*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: '@shopify*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - '@remix-run*'
-          - '@shopify*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/ionic-angular-v8
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: '@ionic*'
-      - dependency-name: '@angular*'
-    ignore:
-      - dependency-name: '@ionic*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: '@angular*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - '@angular*'
-          - '@ionic*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/ionic-react-v7
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: '@ionic*'
-      - dependency-name: 'react*'
-    ignore:
-      - dependency-name: '@ionic*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: 'react*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - '@ionic*'
-          - 'react*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/nuxt-v3
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'nuxt'
-      - dependency-name: 'vue'
-      - dependency-name: 'vue-router'
-      - dependency-name: '@nuxt-devtools'
-    ignore:
-      - dependency-name: 'nuxt'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: 'vue'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: 'vue-router'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-      - dependency-name: '@nuxt-devtools'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'nuxt'
-          - 'vue'
-          - 'vue-router'
-          - '@nuxt-devtools'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/parcel-v2
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-      - 'erikareads'
-      - 'jeffsee55'
-      - 'onsclom'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'parcel'
-    ignore:
-      - dependency-name: 'parcel'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'parcel'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/preact-v10
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'preact*'
-    ignore:
-      - dependency-name: 'preact*'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'preact*'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/stencil-v4
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: '@stencil/core'
-    ignore:
-      - dependency-name: '@stencil/core'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - '@stencil/core'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/vite-v5
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'vite'
-    ignore:
-      - dependency-name: 'vite'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'vite'
-        update-types:
-          - 'minor'
-
-  - directory: /packages/static-build/test/fixtures/vitepress
-    schedule:
-      interval: 'daily'
-    open-pull-requests-limit: 1
-    reviewers:
-      - 'trek'
-      - 'TooTallNate'
-      - 'EndangeredMassa'
-      - 'jefsee55'
-      - 'onsclom'
-      - 'erikareads'
-    commit-message:
-      prefix: '[framework-fixtures]'
-    package-ecosystem: 'npm'
-    allow:
-      - dependency-name: 'vitepress'
-    ignore:
-      - dependency-name: 'vitepress'
-        update-types:
-          ['version-update:semver-major', 'version-update:semver-patch']
-    groups:
-      core:
-        patterns:
-          - 'vitepress'
-        update-types:
-          - 'minor'

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

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

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

@@ -1,8 +1,6 @@
 name: Cron Update Next
 
 on:
-  # Allow manual runs
-  workflow_dispatch:
   # Run every 4 hours https://crontab.guru/every-4-hours
   schedule:
     - cron: '0 */4 * * *'
@@ -12,20 +10,16 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        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@v7
+        uses: actions/github-script@v6
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-          GITHUB_TOKEN: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
         # See https://github.com/actions/github-script#run-a-separate-file-with-an-async-function
         with:
-          github-token: ${{ secrets.GH_TOKEN_PULL_REQUESTS }}
           script: |
             const script = require('./utils/update-next.js')
             await script({ github, context })

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

@@ -1,8 +1,6 @@
 name: Cron Update Turbo
 
 on:
-  # Allow manual runs
-  workflow_dispatch:
   # Run every week https://crontab.guru/every-week
   schedule:
     - cron: '0 0 * * 0'
@@ -12,20 +10,18 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v4
+        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: install pnpm@7.26.0
+        run: npm i -g pnpm@7.26.0
       - name: Create Pull Request
-        uses: actions/github-script@v7
+        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

@@ -16,7 +16,7 @@ jobs:
           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

@@ -16,9 +16,9 @@ jobs:
           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

@@ -16,9 +16,9 @@ jobs:
           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,69 @@
+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
+      timeout-minutes: 5 # See https://github.com/actions/cache/issues/810
+      with:
+        node-version: 14
+    - name: Cache
+      if: ${{ steps.check-release.outputs.IS_RELEASE == 'true' }}
+      uses: actions/cache@v3
+      with:
+        path: '**/node_modules'
+        key: pnpm-${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('pnpm-lock.yaml') }}
+        restore-keys: pnpm-${{ matrix.os }}-${{ matrix.node }}
+    - 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/release.yml

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

.github/workflows/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-18.yml

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

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

@@ -0,0 +1,53 @@
+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: [14]
+    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
+        timeout-minutes: 5 # See https://github.com/actions/cache/issues/810
+        with:
+          node-version: ${{ matrix.node }}
+      - uses: actions/cache@v3
+        with:
+          path: '**/node_modules'
+          key: pnpm-${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: pnpm-${{ matrix.os }}-${{ 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-integration-cli
+        env:
+          VERCEL_TEST_TOKEN: ${{ secrets.VERCEL_TEST_TOKEN }}
+          VERCEL_TEST_REGISTRATION_URL: ${{ secrets.VERCEL_TEST_REGISTRATION_URL }}

.github/workflows/test-lint.yml

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

.github/workflows/test-unit.yml

@@ -0,0 +1,56 @@
+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: [14]
+    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
+        timeout-minutes: 5 # See https://github.com/actions/cache/issues/810
+        with:
+            node-version: ${{ matrix.node }}
+      - uses: actions/cache@v3
+        with:
+          path: '**/node_modules'
+          key: pnpm-${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: pnpm-${{ matrix.os }}-${{ 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

@@ -1,15 +1,15 @@
-name: Tests Node.js v16
+name: Tests
 
 on:
   push:
     branches:
-      - main
+    - main
     tags:
-      - '!*'
+    - '!*'
   pull_request:
 
 env:
-  NODE_VERSION: '16'
+  NODE_VERSION: '14'
   TURBO_REMOTE_ONLY: 'true'
   TURBO_TEAM: 'vercel'
   TURBO_TOKEN: ${{ secrets.TURBO_TOKEN }}
@@ -26,14 +26,23 @@ jobs:
       tests: ${{ steps['set-tests'].outputs['tests'] }}
       dplUrl: ${{ steps.waitForTarball.outputs.url }}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 2
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-go@v3
+        with:
+          go-version: '1.13.15'
+      - uses: actions/setup-node@v3
+        timeout-minutes: 5 # See https://github.com/actions/cache/issues/810
         with:
           node-version: ${{ env.NODE_VERSION }}
-      - name: install pnpm@8.3.1
-        run: npm i -g pnpm@8.3.1
+      - uses: actions/cache@v3
+        with:
+          path: '**/node_modules'
+          key: pnpm-${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: pnpm-${{ matrix.os }}-${{ matrix.node }}
+      - name: install pnpm@7.24.2
+        run: npm i -g pnpm@7.24.2
       - run: pnpm install
       - id: set-tests
         run: |
@@ -41,12 +50,13 @@ jobs:
           echo "Files to test:"
           echo "$TESTS_ARRAY"
           echo "tests=$TESTS_ARRAY" >> $GITHUB_OUTPUT
-      - uses: patrickedqvist/wait-for-vercel-preview@bfdff514ff78a669f2536e9f4dd4ef5813a704a2
+      - 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 }}
@@ -59,66 +69,49 @@ jobs:
       matrix:
         include: ${{ fromJson(needs.setup.outputs['tests']) }}
     steps:
-      - uses: actions/checkout@v4
+      - uses: actions/checkout@v3
         with:
           fetch-depth: 2
-      - uses: actions/setup-node@v4
+      - uses: actions/setup-go@v3
         with:
-          node-version: ${{ matrix.nodeVersion || env.NODE_VERSION }}
+          go-version: '1.13.15'
+      - uses: actions/setup-node@v3
+        timeout-minutes: 5 # See https://github.com/actions/cache/issues/810
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - uses: actions/cache@v3
+        with:
+          path: '**/node_modules'
+          key: pnpm-${{ matrix.os }}-${{ matrix.node }}-${{ hashFiles('pnpm-lock.yaml') }}
+          restore-keys: pnpm-${{ matrix.os }}-${{ matrix.node }}
 
-      # yarn 1.22.21 introduced a Corepack bug when running tests.
-      # this can be removed once https://github.com/yarnpkg/yarn/issues/9015 is resolved
-      - name: install yarn@1.22.19
-        run: npm i -g yarn@1.22.19
+      - name: Install 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@8.3.1
-        run: npm i -g pnpm@8.3.1
+      - 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" --log-order=stream --scope=${{matrix.packageName}} --include-dependencies --no-deps
+        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 ${{matrix.testScript}} --summarize --cache-dir=".turbo" --log-order=stream --scope=${{matrix.packageName}} --no-deps -- ${{ join(matrix.testPaths, ' ') }}
+        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:
-          JEST_JUNIT_OUTPUT_FILE: ${{github.workspace}}/.junit-reports/${{matrix.scriptName}}-${{matrix.packageName}}-${{matrix.chunkNumber}}-${{ matrix.runner }}.xml
           VERCEL_CLI_VERSION: ${{ needs.setup.outputs.dplUrl }}/tarballs/vercel.tgz
           VERCEL_TEST_TOKEN: ${{ secrets.VERCEL_TEST_TOKEN }}
           VERCEL_TEST_REGISTRATION_URL: ${{ secrets.VERCEL_TEST_REGISTRATION_URL }}
           FORCE_COLOR: '1'
-      - name: 'Determine Turbo HIT or MISS'
-        if: ${{ !cancelled() }}
-        id: turbo-summary
-        shell: bash
-        run: |
-          TURBO_MISS_COUNT=`node utils/determine-turbo-hit-or-miss.js`
-          echo "MISS COUNT: $TURBO_MISS_COUNT"
-          echo "misses=$TURBO_MISS_COUNT" >> $GITHUB_OUTPUT
-      - name: 'Upload Test Report to Datadog'
-        if: ${{ steps['turbo-summary'].outputs.misses != '0' && !cancelled() }}
-        run: 'npx @datadog/datadog-ci@2.18.1 junit upload --service vercel-cli .junit-reports'
-        env:
-          DATADOG_API_KEY: ${{secrets.DATADOG_API_KEY_CLI}}
-          DD_ENV: ci
 
-  summary:
-    name: Summary
-    runs-on: ubuntu-latest
-    timeout-minutes: 5
-    if: always()
+  conclusion:
     needs:
       - test
+    runs-on: ubuntu-latest
+    name: E2E
     steps:
-      - name: Check All
-        run: |-
-          for status in ${{ join(needs.*.result, ' ') }}
-          do
-            if [ "$status" != "success" ] && [ "$status" != "skipped" ]
-            then
-              echo "Some checks failed"
-              exit 1
-            fi
-          done
+      - name: Done
+        run: echo "Done."

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

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

.gitignore

@@ -31,4 +31,3 @@ __pycache__
 .turbo
 .eslintcache
 turbo-cache-key.json
-junit.xml

.node_version

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

.npmrc

@@ -1,4 +1,3 @@
-provenance=true
 save-exact=true
 hoist-pattern[]=!"**/@types/**"
 hoist-pattern[]=!"**/typedoc"

.nvmrc

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

.prettierignore

@@ -7,30 +7,3 @@ examples/sveltekit-1
 
 # gatsby-plugin-vercel-analytics
 packages/gatsby-plugin-vercel-analytics
-
-# ignore directories that are not source code
-node_modules
-dist
-pnpm-lock.yaml
-.changeset
-.vscode
-.DS_Store
-.next
-.vercel
-.turbo
-.eslintcache
-.output
-.vercel_build_output
-.vercel
-coverage
-turbo-cache-key.json
-/examples
-/public
-packages/*/dist
-packages/*/node_modules
-packages/**/test/fixtures
-packages/**/test/fixtures-*
-packages/**/test/dev/fixtures
-packages/**/test/build-fixtures
-packages/**/test/cache-fixtures
-packages/cli/src/util/dev/templates/*.ts

DEVELOPING_A_RUNTIME.md

@@ -79,23 +79,18 @@ 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.
 
-> Note: Only files within the repo root directory can be cached.
-
 **Example:**
 
 ```typescript
-import { relative } from 'path';
-import { glob, PrepareCache } from '@vercel/build-utils';
+import { PrepareCacheOptions } from '@vercel/build-utils';
 
-export const prepareCache: PrepareCache = async ({
-  workPath,
-  repoRootPath,
-}) => {
+export async function prepareCache(options: PrepareCacheOptions) {
   // Create a mapping of file names and `File` object instances to cache here…
-  const rootDirectory = relative(repoRootPath, workPath);
-  const cache = await glob(`${rootDirectory}/some/dir/**`, repoRootPath);
-  return cache;
-};
+
+  return {
+    'path-to-file': File,
+  };
+}
 ```
 
 ### `shouldServe()`
@@ -385,16 +380,16 @@ This is a [class](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refere
 
 This is an abstract enumeration type that is implemented by one of the following possible `String` values:
 
-- `nodejs20.x`
 - `nodejs18.x`
 - `nodejs16.x`
+- `nodejs14.x`
+- `go1.x`
 - `java11`
 - `python3.9`
 - `dotnet6`
 - `dotnetcore3.1`
 - `ruby2.7`
 - `provided.al2`
-- `provided.al2023`
 
 ## `@vercel/build-utils` Helper Functions
 

README.md

@@ -13,17 +13,19 @@
   <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/docs/cli"><strong>CLI</strong></a>
+  <a href="https://vercel.com/cli"><strong>CLI</strong></a>
 </p>
 <br/>
 
 ## Vercel
 
-Vercel’s Frontend Cloud provides the developer experience and infrastructure to build, scale, and secure a faster, more personalized Web.
+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/docs/cli). Then, `git push` to 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
 
@@ -35,134 +37,7 @@ This project uses [pnpm](https://pnpm.io/) to install dependencies and run scrip
 
 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`.
 
-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](./.github/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 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.
-
-##### Running integration tests locally
-
-While running the full integration suite locally is not recommended, it's sometimes useful to isolate a failing test by running it on your machine. To do so, you'll need to ensure you have the appropriate credentials sourced in your shell:
-
-1. Create an access token. Follow the insructions here https://vercel.com/docs/rest-api#creating-an-access-token. Ensure the token scope is for your personal
-   account.
-2. Grab the team ID from the Vercel dashboard at `https://vercel.com/<MY-TEAM>/~/settings`.
-3. Source these into your shell rc file: `echo 'export VERCEL_TOKEN=<MY-TOKEN> VERCEL_TEAM_ID=<MY-TEAM-ID>' >> ~/.zshrc`
-
-From there, you should be able to trigger an integration test. Choose one
-that's already isolated to check that things work:
-
-```
-cd packages/next
-```
-
-Run the test:
-
-```
-pnpm test test/fixtures/00-server-build/index.test.js
-```
-
-#### @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
+See the [Contributing Guidelines](./.github/CONTRIBUTING.md) for more details.
 
 ## Reference
 

api/CHANGELOG.md

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

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

@@ -51,11 +51,8 @@ export async function getGitHubRepoInfo(repo: Repo) {
     data.subdir = repo.path.slice(subdirPath.length).split('/');
   }
 
-  if (
-    data.id === 'vercel/vercel' &&
-    data.subdir &&
-    data.subdir[0] === 'examples'
-  ) {
+  if (data.id === '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();

api/_lib/script/build.ts

@@ -33,12 +33,7 @@ async function main() {
   });
 
   const existingExamples = exampleDirs
-    .filter(
-      dir =>
-        dir.isDirectory() &&
-        dir.name !== 'node_modules' &&
-        dir.name !== '__tests__'
-    )
+    .filter(dir => dir.isDirectory())
     .map(dir => ({
       name: dir.name,
       visible: true,

api/_lib/util/error-handler.ts

@@ -13,7 +13,7 @@ function initSentry() {
   sentryInitDone = true;
 
   init({
-    // Cannot figure out what's going wrong here. VSCode resolves this fine. But when we build it blows up.
+    // 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',

api/package.json

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

api/tsconfig.json

@@ -1,6 +1,6 @@
 {
   "compilerOptions": {
-    "target": "ES2021",
+    "target": "ES2020",
     "skipLibCheck": true,
     "strict": false,
     "forceConsistentCasingInFileNames": true,

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/"

errors/invalid-route-source.md

@@ -50,4 +50,4 @@ Ensure any segments used in the `destination` property are also used in the `sou
 
 - [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 parameters](https://github.com/pillarjs/path-to-regexp/blob/v6.1.0/Readme.md#unnamed-parameters)
+- [un-named paramters](https://github.com/pillarjs/path-to-regexp/blob/v6.1.0/Readme.md#unnamed-parameters)

errors/missing-env-file.md

@@ -4,7 +4,7 @@
 
 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.local`.
+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.
 
@@ -12,11 +12,11 @@ Read below for how to address this error.
 
 #### Possible Ways to Fix It
 
-The error message will list environment variables that are required and which file they are required to be included in `.env.local`.
+The error message will list environment variables that are required and which file they are required to be included in `.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.local`, then the `.env.local` file should look like this:
+For example, if the error message shows that the environment variable `TEST` is missing from `.env`, then the `.env` file should look like this:
 
 ```
 TEST=value

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

@@ -11,4 +11,4 @@ Remove the `functions` config from your `now.json` or `vercel.json` to take adva
 
 ### Useful Links
 
-- [Functions Config Documentation](https://vercel.com/docs/concepts/projects/project-configuration#functions)
+- [Functions Config Documentation](https://vercel.com/docs/configuration?query=functions#project/functions)

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

@@ -11,6 +11,6 @@ Migrate from using legacy `routes` to the new `rewrites`, `redirects`, and `head
 
 ### 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)
+- [Rewrites Documentation](https://vercel.com/docs/configuration?query=rewrites#project/rewrites)
+- [Redirects Documentation](https://vercel.com/docs/configuration?query=rewrites#project/redirects)
+- [Headers Documentation](https://vercel.com/docs/configuration?query=rewrites#project/headers)

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

@@ -14,9 +14,7 @@ In order to create the smallest possible lambdas Next.js has to be configured to
 npm install next --save
 ```
 
-2. Check [Node.js Version](https://vercel.link/node-version) in your Project Settings. Using an old or incompatible version of Node.js can cause the Build Step to fail with this error message.
-
-3. Add the `now-build` script to your `package.json` [deprecated]
+2. Add the `now-build` script to your `package.json`
 
 ```json
 {
@@ -26,7 +24,7 @@ npm install next --save
 }
 ```
 
-4. Add `target: 'serverless'` to `next.config.js` [deprecated]
+3. Add `target: 'serverless'` to `next.config.js`
 
 ```js
 module.exports = {
@@ -35,9 +33,9 @@ module.exports = {
 };
 ```
 
-5. Remove `distDir` from `next.config.js` as `@vercel/next` can't parse this file and expects your build output at `/.next`
+4. Remove `distDir` from `next.config.js` as `@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`
+5. Optionally make sure the `"src"` in `"builds"` points to your application `package.json`
 
 ```js
 {
@@ -45,5 +43,3 @@ module.exports = {
   "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

@@ -2,15 +2,15 @@
 
 #### Why This Error Occurred
 
-This error is often caused by a misconfigured "Build Command" or "Output Directory" for your Next.js project.
+This could be caused by a 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.
+1. Ensure that the "Build Command" setting is not changed, or that it calls `next build`. If this command is not changed but you are seeing this error, double check that your `build` script in `package.json` calls `next build`.
+2. Ensure that the "Output Directory" setting is not changed. This value almost never needs to be configured, and is only necessary if you override `distDir` in `next.config.js`.
+3. For `next export` users: **do not override the "Output Directory"**. Next.js automatically detects what folder you outputted `next export` to.
 
 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.

examples/CHANGELOG.md

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

examples/README.md

@@ -1,6 +1,6 @@
 # Vercel Examples
 
-To get started using any of these examples as your own project, [install Vercel](https://vercel.com/docs/cli) and use either of the following commands in your terminal:
+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

examples/__tests__/integration/angular.test.ts

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

examples/__tests__/integration/astro.test.ts

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

examples/__tests__/integration/blitzjs.test.ts

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

examples/__tests__/integration/brunch.test.ts

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

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

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

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

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

examples/__tests__/integration/docusaurus.test.ts

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

examples/__tests__/integration/dojo.test.ts

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

examples/__tests__/integration/eleventy.test.ts

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

examples/__tests__/integration/ember.test.ts

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

examples/__tests__/integration/gatsby.test.ts

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

examples/__tests__/integration/gridsome.test.ts

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

examples/__tests__/integration/hexo.test.ts

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

examples/__tests__/integration/hugo.test.ts

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

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

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

examples/__tests__/integration/hydrogen.test.ts

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

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

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

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

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

examples/__tests__/integration/jekyll.test.ts

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

examples/__tests__/integration/middleman.test.ts

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

examples/__tests__/integration/nextjs.test.ts

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

examples/__tests__/integration/node_modules.test.ts

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

examples/__tests__/integration/nuxtjs.test.ts

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

examples/__tests__/integration/parcel.test.ts

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

examples/__tests__/integration/polymer.test.ts

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

examples/__tests__/integration/preact.test.ts

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

examples/__tests__/integration/redwoodjs.test.ts

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

examples/__tests__/integration/remix.test.ts

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

examples/__tests__/integration/saber.test.ts

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

examples/__tests__/integration/sanity.test.ts

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

examples/__tests__/integration/sapper.test.ts

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

examples/__tests__/integration/scully.test.ts

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

examples/__tests__/integration/solidstart-1.test.ts

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

examples/__tests__/integration/solidstart.test.ts

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

examples/__tests__/integration/stencil.test.ts

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

examples/__tests__/integration/storybook.test.ts

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

examples/__tests__/integration/svelte.test.ts

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

examples/__tests__/integration/sveltekit-1.test.ts

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

examples/__tests__/integration/sveltekit.test.ts

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

examples/__tests__/integration/umijs.test.ts

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

examples/__tests__/integration/vite.test.ts

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

examples/__tests__/integration/vitepress.test.ts

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

examples/__tests__/integration/vue.test.ts

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

examples/__tests__/integration/vuepress.test.ts

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

examples/__tests__/integration/zola.test.ts

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

examples/__tests__/test-utils.ts

@@ -1,27 +0,0 @@
-import { basename, join } from 'path';
-import { lstatSync, readdirSync } from 'fs';
-
-export async function deployExample(filename: string) {
-  const { testDeployment } = require('../../test/lib/deployment/test-deployment.js');
-  const example = basename(filename).replace(/\.test\.ts$/, '');
-  await testDeployment(join(process.cwd(), example));
-}
-
-export function getExamples() {
-  const dirname = join(__dirname, '..');
-  const examples = readdirSync(dirname)
-    .map(example =>
-      ({
-        exampleName: example,
-        examplePath: join(dirname, example),
-        testPath: join(dirname, '__tests__', 'integration', `${example}.test.ts`),
-      })
-    )
-    .filter(o =>
-      !o.exampleName.startsWith('.') &&
-      !o.exampleName.startsWith('_') &&
-      o.exampleName !== 'node_modules' &&
-      lstatSync(o.examplePath).isDirectory()
-    );
-  return examples;
-}

examples/__tests__/unit/index.test.ts

@@ -1,8 +0,0 @@
-import { existsSync } from 'fs';
-import { getExamples } from '../test-utils';
-
-describe('should have test for each example', () => {
-  it.each(getExamples())('should exist $exampleName', async ({testPath}) => {
-    expect(existsSync(testPath)).toBeTruthy();
-  });
-});

examples/astro/README.md

@@ -1,14 +1,6 @@
 # Astro
 
-This directory is a brief example of an [Astro](https://astro.build/) site that can be deployed to Vercel with zero configuration. This demo showcases:
-
-- `/` - A static page (pre-rendered)
-- `/ssr` - A page that uses server-side rendering (through [Vercel Edge Functions](https://vercel.com/docs/functions/edge-functions))
-- `/ssr-with-swr-caching` - Similar to the previous page, but also caches the response on the [Vercel Edge Network](https://vercel.com/docs/edge-network/overview) using `cache-control` headers
-- `/image` - Astro [Asset](https://docs.astro.build/en/guides/assets/) using Vercel [Image Optimization](https://vercel.com/docs/image-optimization)
-- `/edge.json` - An Astro API Endpoint that returns JSON data using [Vercel Edge Functions](https://vercel.com/docs/functions/edge-functions)
-
-Learn more about [Astro on Vercel](https://vercel.com/docs/frameworks/astro).
+This directory is a brief example of an [Astro](https://astro.build/) site that can be deployed to Vercel with zero configuration.
 
 ## Deploy Your Own
 
@@ -20,7 +12,21 @@ _Live Example: https://astro-template.vercel.app_
 
 ## Project Structure
 
-Astro looks for `.astro`, `.md`, or `.js` files in the `src/pages/` directory. Each page is exposed as a route based on its file name.
+Inside of your Astro project, you'll see the following folders and files:
+
+```
+/
+├── public/
+│   └── favicon.ico
+├── src/
+│   ├── components/
+│   │   └── Layout.astro
+│   └── pages/
+│       └── index.astro
+└── package.json
+```
+
+Astro looks for `.astro` or `.md` files in the `src/pages/` directory. Each page is exposed as a route based on its file name.
 
 There's nothing special about `src/components/`, but that's where we like to put any Astro/React/Vue/Svelte/Preact components or layouts.
 
@@ -32,10 +38,9 @@ All commands are run from the root of the project, from a terminal:
 
 | Command                | Action                                             |
 | :--------------------- | :------------------------------------------------- |
-| `pnpm install`          | Installs dependencies                              |
-| `pnpm run dev`          | Starts local dev server at `localhost:3000`        |
-| `pnpm run build`        | Build your production site to `./dist/`            |
-| `pnpm run preview`      | Preview your build locally, before deploying       |
-| `pnpm run start`       | Starts a production dev server at  `localhost:3000`     |
-| `pnpm run astro ...`    | Run CLI commands like `astro add`, `astro preview` |
-| `pnpm run astro --help` | Get help using the Astro CLI                       |
+| `npm install`          | Installs dependencies                              |
+| `npm run dev`          | Starts local dev server at `localhost:3000`        |
+| `npm run build`        | Build your production site to `./dist/`            |
+| `npm run preview`      | Preview your build locally, before deploying       |
+| `npm run astro ...`    | Run CLI commands like `astro add`, `astro preview` |
+| `npm run astro --help` | Get help using the Astro CLI                       |

examples/astro/astro.config.mjs

@@ -1,17 +1,4 @@
 import { defineConfig } from 'astro/config';
-// Use Vercel Edge Functions (Recommended)
-import vercel from '@astrojs/vercel/edge';
-// Can also use Serverless Functions
-// import vercel from '@astrojs/vercel/serverless';
-// Or a completely static build
-// import vercel from '@astrojs/vercel/static';
 
-export default defineConfig({
-  output: 'server',
-  experimental: {
-    assets: true
-   },
-  adapter: vercel({
-    imageService: true,
-  }),
-});
+// https://astro.build/config
+export default defineConfig({});

examples/astro/package.json

@@ -7,10 +7,8 @@
     "preview": "astro preview",
     "astro": "astro"
   },
-  "dependencies": {
-    "@astrojs/vercel": "3.8.2",
-    "astro": "^2.10.14",
-    "react": "18.2.0",
-    "web-vitals": "^3.3.1"
+  "devDependencies": {
+    "astro": "^1.6.10",
+    "web-vitals": "^3.1.0"
   }
 }