Does not return nonzero exit code when failed to read a tsconfig

[dimikot]

Here:

update-ts-references/src/update-ts-references.js

Line 219 in 4a7a93d

console.error(`could not read ${tsconfigFilePath}`, error);

The exception is logged, but not rethrown. So the process exit successfully, which means that it's hard to use the tool in e.g. postinstall scripts or in CI.

In the example below, I manually deleted ./tsconfig.json and ran the tool as update-ts-references && echo ok - it printed "ok".

[MKruschke]

Hi @dimikot,
if you or your teammates deleting the tsconfig.json from the root then I think my tool should be the least problem for you. Because your ts check isn't working anymore 😄

Anyway nice catch for improvement! I will add that check for the root tsconfig 👍🏻

Have a nice weekend 👋🏻

[MKruschke]

Hi @dimikot,
I decided to introduce a strict mode by adding the option --strict as command argument. Please us that from now on if you expect to have in every package as well in the root a tsconfig.json to be present.