【问题标题】:Deploying NextJS to Vercel failed将 NextJS 部署到 Vercel 失败
【发布时间】:2021-08-01 04:10:59
【问题描述】:

我正在尝试将应用程序部署到 Vercel,并在构建时收到此错误

14:13:58.168    Cloning github.com/ChrisB007/moodflics (Branch: main, Commit: 7a2acfe)
14:13:58.575    Cloning completed: 406.06ms
14:13:58.624    Analyzing source code...
14:13:59.946    Installing build runtime...
14:14:03.139    Build runtime installed: 3.193s
14:14:07.055    Build cache not provided
14:14:08.517    Installing dependencies...
14:14:09.142    npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
14:14:23.664    npm WARN moodflics@0.1.0 No repository field.
14:14:23.676    npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents):
14:14:23.677    npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
14:14:23.681    added 387 packages from 281 contributors in 14.582s
14:14:23.836    62 packages are looking for funding
14:14:23.836      run `npm fund` for details
14:14:23.861    Detected Next.js version: 10.2.0
14:14:23.864    Running "npm run build"
14:14:24.144    > moodflics@0.1.0 build /vercel/path0
14:14:24.144    > next build
14:14:24.557    warn  - React 17.0.1 or newer will be required to leverage all of the upcoming features in Next.js 11. Read more: https://nextjs.org/docs/messages/react-version
14:14:24.912    info  - Using webpack 5. Reason: no custom webpack configuration in next.config.js https://nextjs.org/docs/messages/webpack5
14:14:25.052    info  - Checking validity of types...
14:14:25.068    Attention: Next.js now collects completely anonymous telemetry regarding usage.
14:14:25.068    This information is used to shape Next.js' roadmap and prioritize features.
14:14:25.068    You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
14:14:25.068    https://nextjs.org/telemetry
14:14:25.123    info  - Creating an optimized production build...
14:14:29.905    Failed to compile.
14:14:29.906    ModuleNotFoundError: Module not found: Error: Can't resolve 'next-auth/client' in '/vercel/path0/pages'
14:14:29.906    > Build error occurred
14:14:29.907    Error: > Build failed because of webpack errors
14:14:29.907        at /vercel/path0/node_modules/next/dist/build/index.js:17:924
14:14:29.907        at async Span.traceAsyncFn (/vercel/path0/node_modules/next/dist/telemetry/trace/trace.js:6:584)
14:14:29.946    npm ERR! code ELIFECYCLE
14:14:29.947    npm ERR! errno 1
14:14:29.951    npm ERR! moodflics@0.1.0 build: `next build`
14:14:29.951    npm ERR! Exit status 1
14:14:29.951    npm ERR! 
14:14:29.951    npm ERR! Failed at the moodflics@0.1.0 build script.
14:14:29.951    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
14:14:29.959    npm ERR! A complete log of this run can be found in:
14:14:29.959    npm ERR!     /vercel/.npm/_logs/2021-05-10T18_14_29_952Z-debug.log
14:14:29.972    Error: Command "npm run build" exited with 1

在本地似乎一切正常,但是当我尝试将其部署到 Vercel 时,我收到了上述错误消息。能告诉我怎么解决吗?

【问题讨论】:

    标签: next.js vercel next-auth


    【解决方案1】:

    有时 Vercel 会认为我的代码在本地运行(npm run dev)但在上传后失败。当我使用 Github 自动部署时会发生这种情况,即我直接推送到我的 Github 存储库,然后 Vercel 自动构建和更新。

    但是,使用 Vercel CLI 解决了我的问题。运行 vercel 进行预览,然后运行 ​​vercel --prod 进行生产部署

    【讨论】:

    • 很棒的技巧,你也可以运行vercel dev在生产环境中本地测试你的api路由。您的代码库仍在开发中,没有 pages/api/* 路由。它们的行为就像在生产中一样(测试版功能)。如果需要特定端口,请使用vercel dev --listen 5005(或默认端口 3000 以外的任何端口)
    【解决方案2】:
    • 删除node_modules并运行yarn install
    • 然后做yarn build
    • 如果您使用npm,则使用npm inpm run build 而不是yarn installyarn build
    • 然后部署

    【讨论】:

      【解决方案3】:

      无法解析下一个身份验证/客户端

      ModuleNotFoundError: Module not found: Error: Can't resolve 'next-auth/client' in '/vercel/path0/pages'
      

      确保将 next-auth 作为依赖项而不是 dev 依赖项正确安装。还要升级你的反应版本,它会发出警告,说明它不是 17.01 或更高版本。如果您使用的是 typescript,请尝试通过 next-auth 名称空间进行模块扩充,如他们的 typescript 名称空间文档中所示。例如,@/types/next.d.ts 文件和module augmentation 的@/types/next-auth.d.ts 文件。

      在本地,我也使用 nextauth,并且在我的 @/types/next.d.ts 文件中有以下内容:

      
      import type { NextComponentType, NextPageContext } from 'next';
      import type { Session } from 'next-auth';
      import type { Router } from 'next/router';
      
      declare module 'next/app' {
          type AppProps<P = Record<string, unknown>> = {
              Component: NextComponentType<NextPageContext, any, P>;
              router: Router;
              __N_SSG?: boolean;
              __N_SSP?: boolean;
              pageProps: P & {
                  /** Initial session passed in from getServerSideProps or getInitialProps */
                  session?: Session;
              };
          };
      }
      

      至于我的 @/types/next-auth.d.ts 文件的内容,它用于自定义无头 wordpress 身份验证流程,但无论您是否使用自定义方法,您都可以自定义会话/用户界面

      import NextAuth, { User } from 'next-auth';
      import { JWT } from 'next-auth/jwt';
      import { WordpressUserPartialFragment } from '../graphql/generated/graphql';
      declare module 'next-auth' {
          interface Session extends WordpressUserPartialFragment {
              response: {
                  accessToken: string;
                  id: string;
                  avatar: {
                      url: string;
                  };
                  description: string | null;
                  slug: string;
                  username: string;
                  email: string;
                  firstName: string;
                  lastName: string;
                  token_exp: string;
                  refresh_token: string;
                  locale: string;
              };
          }
      }
      
      

      【讨论】:

      • 这是一个很好的答案,干得好!
      猜你喜欢
      • 2022-01-02
      • 2023-01-18
      • 2021-02-17
      • 2021-05-31
      • 1970-01-01
      • 2021-04-22
      • 1970-01-01
      • 2022-12-20
      • 1970-01-01
      相关资源
      最近更新 更多