Failed to build on GitHub Actions with Next.js 12.3

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:19:52 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.14.2
      npm: 8.7.0
      Yarn: 1.22.10
      pnpm: 6.11.0
    Relevant packages:
      next: 12.3.2-canary.7
      eslint-config-next: N/A
      react: 17.0.2
      react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

npm run build is keep failing with the following error message on GitHub Actions, however, it’s build success on my computer and Vercel:

info  - Compiled successfully
info  - Collecting page data...
TypeError [ERR_INVALID_URL]: Invalid URL
    at new NodeError (node:internal/errors:371:5)
    at onParseError (node:internal/url:5[52](https://github.com/thematters/matters-web/actions/runs/3111145523/jobs/5043100695#step:9:52):9)
    at new URL (node:internal/url:628:5)
    at Object.6926 (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:44:1)
    at __webpack_require__ (/home/runner/work/matters-web/matters-web/.next/server/webpack-runtime.js:25:42)
    at __webpack_exec__ (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:168:39)
    at /home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:169:71
    at Function.__webpack_require__.X (/home/runner/work/matters-web/matters-web/.next/server/webpack-runtime.js:207:21)
    at /home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:169:47
    at Object.<anonymous> (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:172:3) {
  input: 'undefined',
  code: 'ERR_INVALID_URL'
}
TypeError [ERR_INVALID_URL]: Invalid URL
    at new NodeError (node:internal/errors:371:5)
    at onParseError (node:internal/url:552:9)
    at new URL (node:internal/url:628:5)
    at Object.6926 (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:44:1)
    at __webpack_require__ (/home/runner/work/matters-web/matters-web/.next/server/webpack-runtime.js:25:42)
    at __webpack_exec__ (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:168:39)
    at /home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:169:71
    at Function.__webpack_require__.X (/home/runner/work/matters-web/matters-web/.next/server/webpack-runtime.js:207:21)
    at /home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:169:47
    at Object.<anonymous> (/home/runner/work/matters-web/matters-web/.next/server/pages/_document.js:172:3) {
  input: 'undefined',
  code: 'ERR_INVALID_URL'
}
> Build error occurred
Error: Failed to collect page data for /404
    at /home/runner/work/matters-web/matters-web/node_modules/next/dist/build/utils.js:916:15
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  type: 'Error'
}

Expected Behavior

Build successfully

Link to reproduction

https://github.com/thematters/matters-web/pull/2766

To Reproduce

Run npm run build on both GitHub Actions and local computer.

[SukkaW]

@robertu7

The new URL is introduced by ~/enum/csp, which is being used in _document. That’s how I found it.

AFAIK Next.js doesn’t change _document parts recently, it is more likely related to how Next.js 12.3 handles .env.* files.

[github-actions[bot]]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.