npm error Cannot read properties of null (reading 'edgesOut')

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

This is not just a request to bump a dependency for a CVE

• This is not solely a request to bump a dependency for a CVE

Current Behavior

I am using npm 10.9.4 version and I am getting the avbove error in the screenshot in the pipleine and local please help me to fix the issue.

{
"name": "daily-plan-ui",
"version": "50.0.0",
"private": true,
"type": "module",
"dependencies": {
"@azure/msal-browser": "^4.26.2",
"@azure/msal-react": "^3.0.22",
"@dnd-kit/core": "^6.3.1",
"@dnd-kit/react": "^0.1.20",
"@dnd-kit/sortable": "^10.0.0",
"@fortawesome/fontawesome-svg-core": "^7.2.0",
"@fortawesome/free-solid-svg-icons": "^7.2.0",
"@fortawesome/react-fontawesome": "^3.3.1",
"@microsoft/applicationinsights-react-js": "^17.3.3",
"@microsoft/applicationinsights-web": "^3.3.3",
"@opentelemetry/api": "^1.9.1",
"@opentelemetry/exporter-trace-otlp-proto": "^0.221.0",
"@opentelemetry/instrumentation": "^0.221.0",
"@opentelemetry/instrumentation-document-load": "^0.66.0",
"@opentelemetry/instrumentation-fetch": "^0.221.0",
"@opentelemetry/instrumentation-user-interaction": "^0.65.0",
"@opentelemetry/instrumentation-xml-http-request": "^0.221.0",
"@opentelemetry/resources": "^2.10.0",
"@opentelemetry/sdk-trace-base": "^2.10.0",
"@opentelemetry/sdk-trace-web": "^2.10.0",
"@reduxjs/toolkit": "^2.2.8",
"@tanstack/react-table": "^8.21.3",
"@tanstack/react-virtual": "^3.13.12",
"@types/node": "^22.14.1",
"@types/pako": "^2.0.4",
"@types/react": "^18.3.11",
"@types/react-dom": "^18.3.0",
"@types/react-virtualized": "^9.22.2",
"@vitejs/plugin-react-swc": "^3.9.0",
"bootstrap": "^5.3.3",
"lodash": "^4.17.23",
"luxon": "^3.5.0",
"pako": "^2.1.0",
"react": "^18.3.1",
"react-datepicker": "^4.23.0",
"react-dnd": "^16.0.1",
"react-dnd-html5-backend": "^16.0.1",
"react-dom": "^18.3.1",
"react-intersection-observer": "^10.0.0",
"react-redux": "^9.1.2",
"react-router-dom": "^6.30.3",
"react-select": "^5.8.1",
"react-switch": "^7.0.0",
"react-virtualized": "^9.22.6",
"reactstrap": "^9.2.3",
"typescript": "^5.6.2",
"vite": "^6.3.2",
"vite-plugin-svgr": "^4.3.0",
"vite-tsconfig-paths": "^5.1.4",
"xlsx": "https://cdn.sheetjs.com/xlsx-0.20.3/xlsx-0.20.3.tgz"
},
"engines": {
"node": ">=22 <24",
"npm": ">=10.9 < 11"
},
"devDependencies": {
"@eslint/eslintrc": "^3.3.3",
"@eslint/js": "^9.39.2",
"@testing-library/jest-dom": "^6.9.1",
"@testing-library/react": "^16.3.2",
"@testing-library/user-event": "^14.6.1",
"@typescript-eslint/eslint-plugin": "^8.59.3",
"@typescript-eslint/parser": "^8.59.3",
"@vitest/coverage-v8": "^4.1.6",
"@vitest/ui": "^4.1.6",
"eslint": "9.39.2",
"eslint-config-prettier": "^10.1.8",
"eslint-plugin-prettier": "^5.5.5",
"eslint-plugin-react": "^7.37.5",
"eslint-plugin-vitest": "^0.5.4",
"husky": "^9.1.7",
"jsdom": "^27.4.0",
"lint-staged": "^16.2.7",
"msw": "^2.12.7",
"prettier": "^3.8.1",
"react-select-event": "^5.5.1",
"vitest": "^4.1.6"
},
"scripts": {
"start": "vite",
"build": "vite build",
"test": "vitest",
"test:coverage": "vitest run --coverage --watch=false",
"test:ci": "vitest run --coverage --watch=false --silent",
"test:cd": "vitest run --watch=false --silent",
"test:ui": "npm run test -- --ui --coverage",
"lint": "eslint ./src",
"lint:fix": "eslint --fix ./src",
"format": "prettier --write .",
"prepare": "husky"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
},
"lint-staged": {
"**/*": "prettier --write --ignore-unknown"
}
}

Expected Behavior

No response

Steps To Reproduce

1. In this environment...
2. With this config...
3. Run '...'
4. See error...

Environment

• npm:
• Node.js:
• OS Name:
• System Model Name:
• npm config:

; copy and paste output from `npm config ls` here

Start with the supplied package.json and collect the missing npm, Node.js, OS, npm config, exact command, and full stack trace. Reproduce the failure locally and in the pipeline with this dependency set, then reduce it to a minimal project. Done means a confirmed trigger and a regression test or sufficiently specific diagnosis.