stream error while trying to build vscode-java@1.7.0

Getting Cannot call write after a stream was destroyed error while trying to use vscode-java@1.7.0 which I built locally

Environment

• Operating System: macOS Catalina
• JDK version: java version "1.8.0_281" and Java(TM) SE Runtime Environment (build 1.8.0_281-b09)
• Visual Studio Code version: 1.69
• Java extension version: 1.7.0

Steps To Reproduce

I have built vscode-java@1.7.0 locally by following the instructions here: https://github.com/redhat-developer/vscode-java/blob/v1.7.0/CONTRIBUTING.md

1. For Client side setup, cloned the vscode-java and checked out to v1.7.0 and then ran npm install
2. For Server side setup, just download the latest snapshot by running the command ./node_modules/.bin/gulp download_server
3. Then ran vsce package which generated a .vsix file
4. Trying to launch the built extension which results with the following error:

Current Result

plugins/redhat-java-features/extension/dist/extension.js:2:1044055 root ERROR [hosted-plugin: 15563] Promise rejection not handled in one second: Error: write EPIPE , reason: Error: write EPIPE With stack trace: Error: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16) root ERROR [hosted-plugin: 15563] Promise rejection not handled in one second: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed , reason: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed root ERROR [hosted-plugin: 15563] With stack trace: Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed at doWrite (_stream_writable.js:399:19) at writeOrBuffer (_stream_writable.js:387:5) at Socket.Writable.write (_stream_writable.js:318:11)

In addition, the extension keeps on loading without showing any syntax errors.

How to resolve this issue ?
Please point me if I am building it incorrectly ?

Reproduce the local build using CONTRIBUTING.md, npm install, gulp download_server, and vsce package, then launch the generated .vsix. Start by examining the stream errors reported from plugins/redhat-java-features/extension/dist/extension.js; done means the locally built extension launches without the EPIPE or ERR_STREAM_DESTROYED errors.