npm / npm/cli

[BUG] Problem with project GatsbyJS generation

Open
#8,560 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

Is there an existing issue for this?
  • I have searched the existing issues
This issue exists in the latest npm version
  • I am using the latest npm
Current Behavior

When you generate a new project via the console using the command gatsby new and enter the initial data, the following texts are displayed at the end of the process in the terminal: ✔ Created site from template
▸ Installing Gatsby...

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues

ERROR UNKNOWN

Command failed with exit code 1: npm install --loglevel error --color always --legacy-peer-deps --no-audit

Translated with DeepL.com (free version)

Expected Behavior

The completion of the process of generating a new local site in GatsbyJS

Steps To Reproduce
  1. In this environment:
    2.Distributor ID: Ubuntu
    Description: Ubuntu 24.04.3 LTS
    Release: 24.04
    Codename: noble

  2. With this config...

  3. Run: gatsby new

  4. See error:

  5. What would you like to call your site?
    ✔ · Calendar VeneHindustrial
    What would you like to name the folder where your site will be created?
    ✔ VeneHindustrial/ calendar_v0.2
    ✔ Will you be using JavaScript or TypeScript?
    · TypeScript
    ✔ Will you be using a CMS?
    · Netlify CMS
    ✔ Would you like to install a styling system?
    · Tailwind CSS
    ✔ Would you like to install additional features with other plugins?
    · Add the Google gtag script for e.g. Google Analytics
    · Add responsive images
    · Add an automatic sitemap
    · Generate a manifest file

Thanks! Here's what we'll now do:

🛠  Create a new Gatsby site in the folder calendar_v0.2
📚 Install and configure the plugin for Netlify CMS
🎨 Get you set up to use Tailwind CSS for styling your site
🔌 Install gatsby-plugin-google-gtag, gatsby-plugin-image, gatsby-plugin-sitemap, gatsby-plugin-manifest, gatsby-plugin-mdx

✔ Created site from template
▸ Installing Gatsby...

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error https://github.com/npm/cli/issues

ERROR UNKNOWN

Command failed with exit code 1: npm install --loglevel error --color always --legacy-peer-deps --no-audit

Image
Environment
  • npm: 10.9.3
  • Node.js: v22.18.0
  • OS Name: Ubuntu 24.04.3 LTS
  • System Model Name: Lenovo Intel core 5 + VMWare 16.0
  • npm config:
; copy and paste output from `npm config ls` here

; node bin location = /home/llabori/.nvm/versions/node/v22.18.0/bin/node
; node version = v22.18.0
; npm local prefix = /home/llabori/Documents/VeneHindustrial
; npm version = 10.9.3
; cwd = /home/llabori/Documents/VeneHindustrial
; HOME = /home/llabori
; Run npm config ls -l to show all defaults.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no repository files or tests. Start by reproducing gatsby new on Ubuntu 24.04.3 with Node.js 22.18.0 and npm 10.9.3, then inspect the failing npm install --loglevel error --color always --legacy-peer-deps --no-audit invocation; done means determining whether npm CLI is responsible and defining a repository-scoped fix or disposition.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.