Error does not result in non-zero exit code

[kumavis]

$ ./node_modules/patch-package/index.js     
patch-package 6.2.2
Applying patches...
depd@1.1.2 ✔
ethereumjs-abi/keccak@2.1.0 ✔
ethereumjs-tx/keccak@2.1.0 ✔
keccak@1.4.0 ✔
secp256k1@3.8.0 ✔
Error: Patch file found for package keccak which is not present at node_modules/web3-provider-engine/node_modules/keccak

results in exit code zero

this should report a non-zero exit code

related #210

[kumavis]

looks like it is intentional #86
workaround is NODE_ENV=test

[codepainters]

Unbelievable, that ignoring an error is actually intended - I've just struggled with strange errors in a project, because I wasn't aware of a patch not being applied.

If yarn leaves the working directory in an inconsistent state after postinstall script failure, it's yarn's issue.

[joeyparis]

I understand why running this local ends in a zero exit code, but is there anything we can do so it outputs to the yarn install log?