Skip to content

Pages Gatsby does not work at all

Summary

Built-in Gatsby pages on GitLab Pages does not work. Users fail to deploy even by triggering GitLab CI pipeline.

Steps to reproduce

  1. Visit New project and select Create from template tab.
  2. Find Pages/Gatsby and click Use template to create a project.
  3. Run a new pipeline on that created project and then see the failed job.

Example Project

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

$ node_modules/.bin/gatsby build --prefix-paths
/builds/tnir/pages-gatsby-20200607/node_modules/gatsby-cli/lib/create-cli.js:115
      const args = { ...argv,
                     ^^^
SyntaxError: Unexpected token ...
    at Object.exports.runInThisContext (vm.js:76:16)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (/builds/tnir/pages-gatsby-20200607/node_modules/gatsby-cli/lib/index.js:14:18)
    at Module._compile (module.js:570:32)

Output of checks

This bug happens on GitLab.com (at least GitLab 13.0 through 13.2).

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Part of #220679 (closed)

Edited by Takuya Noguchi