Pete Bacon Darwin cabf997933 fix(ngcc): display unlocker process output in sync mode (#36637) ... The change in e041ac6f0d to support sending unlocker process output to the main ngcc console output prevents messages require that the main process relinquishes the event-loop to allow the `stdout.on()` handler to run. This results in none of the messages being written when ngcc is run in `--no-async` mode, and some messages failing to be written if the main process is killed (e.g. ctrl-C). It appears that the problem with Windows and detached processes is known - see https://github.com/nodejs/node/issues/3596#issuecomment-250890218. But in the meantime, this commit is a workaround, where non-Windows `inherit` the main process `stdout` while on Windows it reverts to the async handler approach, which is better than nothing. PR Close #36637		2020-04-16 16:05:12 -04:00
..
integrationtest	build: reformat repo to new clang@1.4.0 (#36613)	2020-04-14 12:08:36 -07:00
ngcc	fix(ngcc): display unlocker process output in sync mode (#36637)	2020-04-16 16:05:12 -04:00
src	fix(compiler): handle type references to namespaced symbols correctly (#36106)	2020-04-09 11:32:21 -07:00
test	fix(compiler): avoid generating i18n attributes in plain form (#36422)	2020-04-16 09:44:10 -07:00
BUILD.bazel	build: provide full paths to `ts_api_guardian_test_npm_package` and `ts_api_guardian_test` (#36034)	2020-03-12 09:49:00 -07:00
index.ts	refactor(compiler-cli): Move diagnostics files to language service (#33809)	2019-11-14 09:29:07 -08:00
package.json	fix(compiler-cli): TypeScript peer dependency range (#36008)	2020-03-11 14:44:48 -04:00
tsconfig-build.json	build: reference zone.js from source directly instead of npm. (#33046)	2019-11-06 00:48:34 +00:00
tsconfig.json	perf(ivy): ngcc - only find dependencies when targeting a single entry-point (#30525)	2019-07-09 09:40:46 -07:00