[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-3852":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":15,"starSnapshotCount":15,"syncStatus":35,"lastSyncTime":36,"discoverSource":37},3852,"vercel","vercel\u002Fvercel","Develop. Preview. Ship.","https:\u002F\u002Fvercel.com",null,"TypeScript",15643,3627,229,292,0,3,37,177,23,45,"Apache License 2.0",false,"main",true,[26,27,28,29,30,31,5],"cli","cloud","command","hosting","jamstack","ship","2026-06-12 02:00:55","\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fvercel.com\">\n    \u003Cimg src=\"https:\u002F\u002Fassets.vercel.com\u002Fimage\u002Fupload\u002Fv1588805858\u002Frepositories\u002Fvercel\u002Flogo.png\" height=\"96\">\n    \u003Ch3 align=\"center\">Vercel\u003C\u002Fh3>\n  \u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  Develop. Preview. Ship.\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"https:\u002F\u002Fvercel.com\u002Fdocs\">\u003Cstrong>Documentation\u003C\u002Fstrong>\u003C\u002Fa> ·\n  \u003Ca href=\"https:\u002F\u002Fvercel.com\u002Fchangelog\">\u003Cstrong>Changelog\u003C\u002Fstrong>\u003C\u002Fa> ·\n  \u003Ca href=\"https:\u002F\u002Fvercel.com\u002Ftemplates\">\u003Cstrong>Templates\u003C\u002Fstrong>\u003C\u002Fa> ·\n  \u003Ca href=\"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli\">\u003Cstrong>CLI\u003C\u002Fstrong>\u003C\u002Fa>\n\u003C\u002Fp>\n\u003Cbr\u002F>\n\n## Vercel\n\nVercel’s AI Cloud is a unified platform for building modern applications, giving teams the tools to be flexible, move fast, and stay secure while focusing on their products instead of infrastructure.\n\n## Deploy\n\nGet started by [importing a project](https:\u002F\u002Fvercel.com\u002Fnew), [choosing a template](https:\u002F\u002Fvercel.com\u002Ftemplates), or using the [Vercel CLI](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcli). Then, `git push` to deploy.\n\n## Documentation\n\nFor details on how to use Vercel, check out our [documentation](https:\u002F\u002Fvercel.com\u002Fdocs).\n\n## Contributing\n\nThis project uses [pnpm](https:\u002F\u002Fpnpm.io\u002F) to install dependencies and run scripts.\n\nYou can use the `vercel` script to run local changes as if you were invoking Vercel CLI. For example, `vercel deploy --cwd=\u002Fpath\u002Fto\u002Fproject` could be run with local changes with `pnpm vercel deploy --cwd=\u002Fpath\u002Fto\u002Fproject`.\n\nWhen contributing to this repository, please first discuss the change you wish to make via [Vercel Community](https:\u002F\u002Fcommunity.vercel.com\u002Ftags\u002Fc\u002Fcommunity\u002F4\u002Fcli) with the owners of this repository before submitting a Pull Request.\n\nPlease read our [Code of Conduct](.\u002F.github\u002FCODE_OF_CONDUCT.md) and follow it in all your interactions with the project.\n\n### Local development\n\nThis project is configured in a monorepo, where one repository contains multiple npm packages. Dependencies are installed and managed with `pnpm`, not `npm` CLI.\n\nTo get started, execute the following:\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel\ncd vercel\ncorepack enable\npnpm install\npnpm build\npnpm lint\npnpm test-unit\n```\n\nMake sure all the tests pass before making changes.\n\n#### Running Vercel CLI Changes\n\nYou can use `pnpm vercel` from the `cli` package to invoke Vercel CLI with local changes:\n\n```bash\ncd .\u002Fpackages\u002Fcli\npnpm vercel \u003Ccli-commands...>\n```\n\nSee [CLI Local Development](..\u002Fpackages\u002Fcli#local-development) for more details.\n\n### Verifying your change\n\nOnce you are done with your changes (we even suggest doing it along the way), make sure all the tests still pass by running:\n\n```bash\npnpm test-unit\n```\n\nfrom the root of the project.\n\nIf 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.\n\n### Pull Request Process\n\nOnce you are confident that your changes work properly, open a pull request on the main repository.\n\nThe pull request will be reviewed by the maintainers and the tests will be checked by our continuous integration platform.\n\n### Interpreting test errors\n\nThere are 2 kinds of tests in this repository – Unit tests and Integration tests.\n\nUnit tests are run locally with `jest` and execute quickly because they are testing the smallest units of code.\n\n#### Integration tests\n\nIntegration 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:\n\n```log\n[Error: Fetched page https:\u002F\u002Ftest-8ashcdlew.vercel.app\u002Froot.js does not contain hello Root!. Instead it contains An error occurred with this application.\n\n    NO_STATUS_CODE_FRO Response headers:\n       cache-control=s-maxage=0\n      connection=close\n      content-type=text\u002Fplain; charset=utf-8\n      date=Wed, 19 Jun 2019 18:01:37 GMT\n      server=now\n      strict-transport-security=max-age=63072000\n      transfer-encoding=chunked\n      x-now-id=iad1:hgtzj-1560967297876-44ae12559f95\n      x-now-trace=iad1]\n```\n\nIn such cases, you can visit the URL of the failed deployment and append `\u002F_logs` to see the build error. In the case above, that would be https:\u002F\u002Ftest-8ashcdlew.vercel.app\u002F_logs\n\nThe logs of this deployment will contain the actual error which may help you to understand what went wrong.\n\n##### Running integration tests locally\n\nWhile 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:\n\n1. Create an access token. Follow the instructions here https:\u002F\u002Fvercel.com\u002Fdocs\u002Frest-api#creating-an-access-token. Ensure the token scope is for your personal\n   account.\n2. Grab the team ID from the Vercel dashboard at `https:\u002F\u002Fvercel.com\u002F\u003CMY-TEAM>\u002F~\u002Fsettings`.\n3. Source these into your shell rc file: `echo 'export VERCEL_TOKEN=\u003CMY-TOKEN> VERCEL_TEAM_ID=\u003CMY-TEAM-ID>' >> ~\u002F.zshrc`\n\nFrom there, you should be able to trigger an integration test. Choose one\nthat's already isolated to check that things work:\n\n```bash\ncd packages\u002Fnext\n```\n\nRun the test:\n\n```bash\npnpm test test\u002Ffixtures\u002F00-server-build\u002Findex.test.js\n```\n\n> [!NOTE]\n> If you receive a `401` status code while fetching the deployment, you need to disable [Deployment Protection](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fsecurity\u002Fdeployment-protection) on the project.\n\n#### @vercel\u002Fnft\n\nSome of the Builders use `@vercel\u002Fnft` 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:\n\n```js\nconst { nodeFileTrace } = require('@vercel\u002Fnft');\nnodeFileTrace(['path\u002Fto\u002Fentrypoint.js'], {\n  ts: true,\n  mixedModules: true,\n})\n  .then(o => console.log(o.fileList))\n  .then(e => console.error(e));\n```\n\nWhen you run this script, you'll see all the imported files. If files are missing, the bug is in [@vercel\u002Fnft](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fnft) and not the Builder.\n\n### Deploy a Builder with existing project\n\nSometimes 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.\n\n1. Change directory to the desired Builder `cd .\u002Fpackages\u002Fnode`\n2. Run `pnpm build` to compile typescript and other build steps\n3. Run `npm pack` to create a tarball file. It is imporant to not use `pnpm pack` because it will not preserve the file permissions\n4. Move the resulting tarball to a directory\n5. Run `vercel \u003Cdirectory>` to upload the tarball file and get a URL. Remember to append `\u002F\u003Ctarball name>` to then end of your URL\n6. Edit any existing `vercel.json` project and replace `use` with the URL\n7. Run `vercel` or `vercel dev` to deploy with the experimental Builder\n\n**Note:** You will need to turn off vercel authentication in settings -> deployment protection so the builder can be downloaded\n\n## Reference\n\n- [Code of Conduct](.\u002F.github\u002FCODE_OF_CONDUCT.md)\n- [Contributing Guidelines](.\u002F.github\u002FCONTRIBUTING.md)\n- [Apache 2.0 License](.\u002FLICENSE)\n","Vercel 是一个集开发、预览和部署于一体的云端平台。它支持通过 CLI 工具快速导入项目或使用模板开始新项目，并允许开发者通过简单的 `git push` 操作实现代码的即时部署，特别强调了对现代应用尤其是 Jamstack 架构的支持。Vercel 采用 TypeScript 编写，具备强大的云托管能力和灵活的安全性设置，适合需要高效迭代且注重用户体验的网站或Web应用程序开发场景。此外，Vercel 提供详尽的文档和活跃的社区支持，帮助用户更好地理解和利用其功能。",2,"2026-06-11 02:56:39","top_language"]