Fresh installation issue

[projenix]

Hello I am having trouble installing this on Mac OS (Apple Silicon).

Getting this error:

Creating a new Ethereum-powered React app in /Users/projenix/Ethereum-dev/ethapp0.

Downloading template files. This might take a moment.

Aborting installation.
Unexpected error. Please report it as a bug:
TypeError: stream.destroy is not a function
at /Users/projenix/.config/yarn/global/node_modules/create-eth-app/dist/index.js:27688:18
at Array.forEach ()
at /Users/projenix/.config/yarn/global/node_modules/create-eth-app/dist/index.js:27686:18
at runMicrotasks ()
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Promise.all (index 0)

error Command failed.
Exit code: 1
Command: /Users/projenix/.yarn/bin/create-eth-app
Arguments:
Directory: /Users/projenix/Ethereum-dev
Output:

info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.

[PaulRBerg]

Hey @projenix! Thanks for reporting.

Reproducing this is a bit tricky for me as I don't have access to an Apple Silicon computer.

Could I kindly ask you to share the following information?

• The exact command you ran
• Whether you ran the command as an administrator or a simple user
• Version of node.js
• Version of operating system

[martinoss]

Exact same error here, but on Windows 10.

[PaulRBerg]

Thanks for reporting, @martinoss! I switched to node v14.15.5 but I couldn't manage to replicate the bug on my Mac. I did however located where the execution halts; it's line 27688 in dist.js.

This might be an issue with either node-promisepipe or got.

[briansoule]

Same issue on macOS intel

[briansoule]

So I think it may have been related to a networking interruption when installing dependencies. I ran yarn global remove create-eth-app and then yarn create eth-app succeeded.

[PaulRBerg]

Thanks for the additional data points, @briansoule.

[PaulRBerg]

While debugging and fixing #135, I bumped into the same error as shared by you guys, stream.destroy is not a function. The error might have been related to the bug I fixed in fcec59d, a fix which has been included in the v1.7.0 release.

Let me know if this keeps happening or not!

[mcsweeneyJA]

bumping as im trying to set up a fresh install and failing with same errors as the people above. On windows 10

[martinoss]

Just checked with 1.7.1, the error is still there