Log more information when a postinstall script fails

[redabacha]

currently it seems deno will only report that a postinstall script has failed and not any reason why as such. other package managers like yarn will dump the stdout/stderr of the postinstall script process to a temporary file on disk which is useful for debugging and it would be great if deno did a similar thing, even if it's just logging directly to the terminal.

[redabacha]

actually with that said, sometimes i see error output but it doesn't always show when running locally. maybe it's related to the loading indicator?

these are two attempts i had running deno install with the esbuild postinstall script failing:

❯ DENO_FUTURE=1 deno install --no-lock --allow-scripts
Warning rimraf@3.0.2 is deprecated: Rimraf versions prior to v4 are no longer supported
Warning glob@7.2.3 is deprecated: Glob versions prior to v9 are no longer supported
Warning inflight@1.0.6 is deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
Warning @humanwhocodes/config-array@0.11.14 is deprecated: Use @eslint/config-array instead
Warning @humanwhocodes/object-schema@2.0.3 is deprecated: Use @eslint/object-schema instead
Download ⣯ [00:22] 1803/1804
error: script 'postinstall' in 'esbuild@0.21.5' failed with exit code 1

here it doesn't show the error message.

and the next time i run it the error message shows:

❯ DENO_FUTURE=1 deno install --no-lock --allow-scripts
Error launching 'deno': Argument list too long (os error 7)
error: script 'postinstall' in 'esbuild@0.21.5' failed with exit code 1

[nathanwhit]

maybe it's related to the loading indicator?

Yeah I think this is correct, it looks like the progress bar is writing over the postinstall script output. I'll look into this