Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot run Gatsby on Mac #26812

Closed
justageek opened this issue Sep 7, 2020 · 4 comments · Fixed by #26824
Closed

Cannot run Gatsby on Mac #26812

justageek opened this issue Sep 7, 2020 · 4 comments · Fixed by #26824
Labels
status: needs reproduction This issue needs a simplified reproduction of the bug for further troubleshooting. topic: cli Related to the Gatsby CLI type: bug An issue or pull request relating to a bug in Gatsby

Comments

@justageek
Copy link

justageek commented Sep 7, 2020

Description

Gatsby cli fails with the following errors

/usr/local/lib/node_modules/gatsby-cli/node_modules/uuid/dist/esm-browser/index.js:1
export { default as v1 } from './v1.js';
^^^^^^

SyntaxError: Unexpected token 'export'
    at wrapSafe (internal/modules/cjs/loader.js:1055:16)
    at Module._compile (internal/modules/cjs/loader.js:1103:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1159:10)
    at Module.load (internal/modules/cjs/loader.js:988:32)
    at Function.Module._load (internal/modules/cjs/loader.js:896:14)
    at Module.require (internal/modules/cjs/loader.js:1028:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/gatsby-cli/node_modules/gatsby-telemetry/lib/telemetry.js:8:13)
    at Module._compile (internal/modules/cjs/loader.js:1139:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1159:10)

Steps to reproduce

Run any Gatsby command

Clear steps describing how to reproduce the issue. Please please please link to a demo project if possible, this makes your issue much easier to diagnose (seriously).

How to Make a Minimal Reproduction: https://www.gatsbyjs.org/contributing/how-to-make-a-reproducible-test-case/

Create a new Gatsby project.
What should happen?

Just the above errors.

What happened.

Mac OS Mojave

Run gatsby info --clipboard in your project directory and paste the output here.

Same errors as described above.

@justageek justageek added the type: bug An issue or pull request relating to a bug in Gatsby label Sep 7, 2020
@gatsbot gatsbot bot added the status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer label Sep 7, 2020
@alandickinson
Copy link

I'm also getting this same error w/ any cli command.

gatsby-cli v2.12.92
node v13.6.0
npm v6.13.4

@GetShortstack
Copy link

I'm having the same issue running any cli command, even gatsby --version

@LekoArts LekoArts added status: needs more info Needs triaging and reproducible examples or more information to be resolved and removed status: triage needed Issue or pull request that need to be triaged and assigned to a reviewer labels Sep 8, 2020
@LekoArts
Copy link
Contributor

LekoArts commented Sep 8, 2020

Please provide some more information like versions of your gatsby-cli, node, npm & operating system.

I've run npm install -g gatsby-cli (with gatsby-cli@2.12.92 on a Ubuntu 18.04 WSL and Node v12.16.2) and can't reproduce this with e.g. gatsby --version.

@LekoArts LekoArts added topic: cli Related to the Gatsby CLI status: needs reproduction This issue needs a simplified reproduction of the bug for further troubleshooting. and removed status: needs more info Needs triaging and reproducible examples or more information to be resolved labels Sep 8, 2020
@LekoArts
Copy link
Contributor

LekoArts commented Sep 8, 2020

This seems related to uuidjs/uuid#488 (comment) - please post your Node version. (with node --version)

pvdz added a commit that referenced this issue Sep 8, 2020
The bump to v8 as applied in #26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes #26812
gatsbybot pushed a commit that referenced this issue Sep 8, 2020
The bump to v8 as applied in #26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes #26812
pragmaticpat pushed a commit to pragmaticpat/gatsby that referenced this issue Apr 28, 2022
…s#26824)

The bump to v8 as applied in gatsbyjs#26636 gave us no benefits and are giving problems with imports in certain cases. Maintainers have made it clear they won't offer any support for node 13, which we will want to support for a while as well.

In due time we'll replace this library with something simpler as the maintenance burden will be too high. For now we revert and pin to 3.4.0, the last stable version that does what we want.

Fixes gatsbyjs#26812
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs reproduction This issue needs a simplified reproduction of the bug for further troubleshooting. topic: cli Related to the Gatsby CLI type: bug An issue or pull request relating to a bug in Gatsby
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants