Yarn throws an error and warnings

[Klaas-Vaak]

Prerequisites

• I read the Deployment and Setup section of the OpenCTI documentation as well as the Troubleshooting page and didn't find anything relevant to my problem.
• I went through old GitHub issues and couldn't find anything relevant
• I googled the issue and didn't find anything relevant

Description

Executing yarn install gives warnings and an error. What should I do to get a clean install?
Thanks in advance for the help.

Environment

1. OS Rocky Linux 8.7
2. OpenCTI version: 5.6.2
3. OpenCTI client: front-end
4. Other environment details:
   Python 3.9.13
   Node v18.14.2
   npm 9.5.0

Additional information

[rob@test opencti]$ sudo yarn install
➤ YN0065: Yarn will periodically gather anonymous telemetry: https://yarnpkg.com/advanced/telemetry
➤ YN0065: Run yarn config set --home enableTelemetry 0 to disable

➤ YN0000: ┌ Resolution step
➤ YN0002: │ @graphql-codegen/cli@npm:3.2.1 [5bd70] doesn't provide @types/node (p68be5), requested by cosmiconfig-typescript-loader
➤ YN0002: │ @graphql-codegen/cli@npm:3.2.1 [5bd70] doesn't provide @types/node (pf9d62), requested by ts-node
➤ YN0002: │ @graphql-codegen/cli@npm:3.2.1 [5bd70] doesn't provide typescript (pd63e7), requested by cosmiconfig-typescript-loader
➤ YN0002: │ @graphql-codegen/cli@npm:3.2.1 [5bd70] doesn't provide typescript (p648bc), requested by ts-node
➤ YN0002: │ @graphql-tools/graphql-tag-pluck@npm:7.5.0 [07b20] doesn't provide @babel/core (pfbbf3), requested by @babel/plugin-syntax-import-assertions
➤ YN0002: │ @whatwg-node/fetch@npm:0.8.2 doesn't provide @types/node (pa9545), requested by @whatwg-node/node-fetch
➤ YN0002: │ opencti-graphql@workspace:. doesn't provide @aws-sdk/abort-controller (p8ccf2), requested by @aws-sdk/lib-storage
➤ YN0060: │ opencti-graphql@workspace:. provides graphql (pebcd9) with version 16.6.0, which doesn't satisfy what graphql-import and some of its descendants request
➤ YN0060: │ opencti-graphql@workspace:. provides graphql (p2c3b2) with version 16.6.0, which doesn't satisfy what merge-graphql-schemas and some of its descendants request
➤ YN0002: │ opencti-graphql@workspace:. doesn't provide webpack (p25690), requested by ts-loader
➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements for details, where is the six-letter p-prefixed code
➤ YN0000: └ Completed in 0s 534ms
➤ YN0000: ┌ Fetch step
➤ YN0013: │ @graphql-tools/import@npm:6.7.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @graphql-tools/json-file-loader@npm:7.4.17 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @graphql-tools/load@npm:7.8.12 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @graphql-tools/merge@npm:8.3.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @graphql-tools/merge@npm:8.3.18 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ ZlibError: zlib: invalid block type
at Unzip.write ([worker eval]:1:357856)
at Unzip.end ([worker eval]:1:357224)
at EventEmitter.write ([worker eval]:1:396317)
at EventEmitter.end ([worker eval]:1:398030)
at parseTar ([worker eval]:1:461136)
at parseTar.next ()
at extractArchiveTo ([worker eval]:1:461426)
at MessagePort. ([worker eval]:1:463334)
➤ YN0013: │ @types/json-schema@npm:7.0.11 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/json-stable-stringify@npm:1.0.34 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/json5@npm:0.0.29 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/jsonwebtoken@npm:9.0.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @types/ldapjs@npm:2.2.5 can't be found in the cache and will be fetched from the remote registry
➤ YN0001: │ ZlibError: zlib: too many length or distance symbols
at Unzip.write ([worker eval]:1:357856)
at Unzip.end ([worker eval]:1:357224)
at EventEmitter.write ([worker eval]:1:396317)
at EventEmitter.end ([worker eval]:1:398030)
at parseTar ([worker eval]:1:461136)
at parseTar.next ()
at extractArchiveTo ([worker eval]:1:461426)
at MessagePort. ([worker eval]:1:463334)
➤ YN0013: │ yn@npm:3.1.1 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:0.1.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ yocto-queue@npm:1.0.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ zen-observable-ts@npm:0.8.21 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ zen-observable@npm:0.8.15 can't be found in the cache and will be fetched from the remote registry
➤ YN0066: │ typescript@patch:typescript@npm%3A4.9.5#~builtin<compat/typescript>::version=4.9.5&hash=bda367: Cannot apply hunk #3
➤ YN0000: └ Completed in 58s 990ms
➤ YN0000: Failed with errors in 59s 527ms

[Klaas-Vaak]

With upgrade to 5.7.0 this doesn't happen anymore