Nestjs/schedule error on npm i

gistfile1.txt

am hitting the following error while installing `@nestjs/schedule`

```
❯ npm i --verbose
npm verb cli /opt/homebrew/Cellar/node/21.6.1/bin/node /opt/homebrew/bin/npm
npm info using npm@10.2.4
npm info using node@v21.6.1
npm verb title npm i
npm verb argv "i" "--loglevel" "verbose"
npm verb logfile logs-max:10 dir:/Users/some_user/.npm/_logs/2024-03-18T19_16_28_591Z-
npm verb logfile /Users/some_user/.npm/_logs/2024-03-18T19_16_28_591Z-debug-0.log
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fschedule 10ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fcommon 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/class-transformer 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/class-validator 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/reflect-metadata 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/rxjs 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fcore 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fmicroservices 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@grpc%2fgrpc-js 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fwebsockets 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fplatform-socket.io 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/amqp-connection-manager 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/amqplib 0ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/cache-manager 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/ioredis 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/kafkajs 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/mqtt 1ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/nats 2ms (cache hit)
npm http fetch GET 200 https://registry.npmjs.org/@nestjs%2fplatform-express 1ms (cache hit)
npm verb stack TypeError: Cannot read properties of null (reading 'edgesOut')
npm verb stack     at #loadPeerSet (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1302:38)
npm verb stack     at async #loadPeerSet (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1321:23)
npm verb stack     at async #buildDepStep (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:917:11)
npm verb stack     at async Arborist.buildIdealTree (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:196:7)
npm verb stack     at async Promise.all (index 1)
npm verb stack     at async Arborist.reify (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:159:5)
npm verb stack     at async Install.exec (/opt/homebrew/lib/node_modules/npm/lib/commands/install.js:152:5)
npm verb stack     at async module.exports (/opt/homebrew/lib/node_modules/npm/lib/cli-entry.js:61:5)
npm verb cwd /Users/some_user/Dropbox (Privat)/some_user/projekte/my_proj/my_proj.server
npm verb Darwin 23.3.0
npm verb node v21.6.1
npm verb npm  v10.2.4
npm ERR! Cannot read properties of null (reading 'edgesOut')
npm verb exit 1
npm verb unfinished npm timer reify 1710789388675
npm verb unfinished npm timer reify:loadTrees 1710789388679
npm verb unfinished npm timer idealTree:buildDeps 1710789388839
npm verb unfinished npm timer idealTree:#root 1710789388839
npm verb code 1
```

and here is my package.json
```
{
  "scripts": {
    "start": "node dist/main.js",
    "start:dev:local": "nest start --watch",
    "start:debug": "nest start --debug --watch",
  },
  "keywords": [],
  "dependencies": {
    "@azure/cosmos": "^4.0.0",
    "@nestjs/common": "*",
    "@nestjs/core": "*",
    "@nestjs/jwt": "^10.2.0",
    "@nestjs/schedule": "4.0.1",
    "@nestjs/platform-express": "^9.0.0",
    "@nestjs/serve-static": "3.0.1",
    "@types/flat": "^5.0.5",
    "@types/lodash": "^4.14.194",
    "@types/qs": "^6.9.11",
    "@types/react": "^18.2.6",
    "@types/react-dom": "^18.2.4",
    "@typescript-eslint/eslint-plugin": "^5.59.5",
    "@typescript-eslint/parser": "^5.59.5",
    "class-transformer": "^0.5.1",
    "compression": "^1.7.4",
    "cookie-parser": "^1.4.6",
    "date-fns": "2.29.3",
    "deep-object-diff": "^1.1.9",
    "flat": "^6.0.1",
    "html-minifier": "^4.0.0",
    "ibantools": "^4.5.0",
    "lodash": "^4.14.194",
    "nano-slots": "^1.4.0",
    "next": "^13.4.2",
    "numeral": "2.0.6",
    "papaparse": "5.4.0",
    "pg": "8.10.0",
    "qs": "^6.11.2",
    "react": "*",
    "react-dom": "^18.2.0",
    "reflect-metadata": "*",
    "rxjs": "^7.2.0",
    "safe-flat": "^2.1.0",
    "tw-elements": "^1.0.0-beta2",
    "typeorm": "^0.3.20",
    "zod": "^3.21.4",
    "zod-form-data": "^2.0.1"
  },
  "devDependencies": {
    "@nestjs/cli": "^9.0.0",
    "@nestjs/schematics": "^9.0.0",
    "@nestjs/testing": "^9.0.0",
    "@types/cookie-parser": "^1.4.6",
    "@types/express": "^4.17.13",
    "@types/jest": "29.2.4",
    "@types/lodash": "^4.14.194",
    "@types/node": "18.11.18",
    "@types/numeral": "^2.0.2",
    "@types/papaparse": "^5.3.14",
    "@types/supertest": "^2.0.11",
    "@types/cron": "^1.7.0",
    "@typescript-eslint/eslint-plugin": "^5.0.0",
    "@typescript-eslint/parser": "^5.0.0",
    "eslint": "^8.0.1",
    "eslint-config-prettier": "^8.10.0",
    "eslint-plugin-prettier": "^4.0.0",
    "jest": "29.3.1",
    "nodemon": "2.0.22",
    "prettier": "^2.3.2",
    "source-map-support": "^0.5.20",
    "supertest": "^6.1.3",
    "ts-jest": "29.0.3",
    "ts-loader": "^9.2.3",
    "ts-node": "^10.0.0",
    "ts-node-dev": "^2.0.0",
    "tsc-alias": "^1.8.6",
    "tsconfig-paths": "^4.1.1",
    "tscpaths": "^0.0.9",
    "typescript": "^4.9.5"
  },
  "peerDependencies": {
    "@nestjs/common": "*",
    "@nestjs/core": "*",
    "express": "^4.17.1",
    "react": "*",
    "reflect-metadata": "*"
  }
}
```

I can overcome the error locally by `npm i --force` however during deployment I dont have that option.

Any pointers on how to overcome this are highly welcome

Thanks