npm / npm/cli

[BUG] Cannot read properties of null (reading 'parent')

Open
#5,047 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage Release 8.x
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

After switching the package to use peer dependencies NPM started showing weird errors in the console:

Error: ✖ Encountered an error when installing package: npm command 'install --save-dev --save-exact --global-style --no-package-lock appium-xcuitest-driver --json' failed with code 1.

STDOUT:


STDERR:
npm ERR! Cannot read properties of null (reading 'parent')
{
  "error": {
    "code": null,
    "summary": "Cannot read properties of null (reading 'parent')",
    "detail": ""
  }
}

The original CI job URL: https://dev.azure.com/AppiumCI/Appium%20CI/_build/results?buildId=22042&view=logs&j=7e827989-f55d-590a-d77d-7047b94f51b2&t=27c7b387-8d59-5d33-b298-5b14b88f552c&l=21

Expected Behavior

The package should be installed without errors

Steps To Reproduce

npm install -g appium@next
appium driver install xcuitest

Environment
  • npm: 8.x (latest from Azure CI)
  • Node.js: 16.x (latest from Azure CI)
  • OS Name: macOS 12
  • System Model Name:
  • npm config:
; copy and paste output from `npm config ls` here

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

Start by reproducing the failure with npm install -g appium@next followed by appium driver install xcuitest under Node.js 16 and npm 8 on macOS. Trace npm's peer-dependency installation path to identify why the package install reads a null parent; done means the driver installs without the reported error and the regression is covered by a relevant test.

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
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.