Fixes#9848.
Root cause of #9848 is unknown, because the cache state file was filled
with nul bytes. It is unclear how that could have happened, but seems
likely to be external interference.
The cascade was that Server failed to start because it would crash when
attempting to load the cache state file. So this fix resolves that by
handling invalid file exceptions.
Fixes#9939.
Uses refactored KeymanSentry.ts in developer-utils and updates the
loader in Server to run from that.
The changes to tray.ts and friends are required to deal with a top-level
await issue with the shutdown call.
The top-level await issue is described in detail at
https://marc.durdin.net/2023/11/dynamic-import-on-node-js-with-circular-dependencies-leads-to-interesting-failure-modes/
tl;dr: shutdown needed to do a proper Sentry shutdown. The shutdown code
was in index.ts. This led to a circular dependency and caused a silent
and abrupt exit code 13 in Node.js. Moved shutdown code into shutdown.ts
to resolve this.
Adds line number context for:
* Error_VirtualCharacterKeysNotSupportedInKeymanWeb
* Error_VirtualKeysNotValidForMnemonicLayouts
* Warn_ExtendedShiftFlagsNotSupportedInKeymanWeb
* Hint_UnreachableKeyCode
* Warn_HelpFileMissing
* Warn_EmbedJsFileMissing
* Error_NotAnyRequiresVersion14
Line number metadata is not easily accessible where the following
messages are generated, so these are a potential future improvement:
* Warn_OptionStoreNameInvalid
* Error_NotSupportedInKeymanWebStore
Fixes#9931.
Provide additional line and file context for some KeymanWeb
compiler messages. This change requires debug data in the intermediate
kmx data provided to the kmw compiler, which should have no impact on
the final .js if debug=false.
This commit only addresses line number data in
Error_NotSupportedInKeymanWebContext and
Error_NotSupportedInKeymanWebOutput.
There are other compiler messages which could benefit from this data:
* Warn_OptionStoreNameInvalid
* Error_VirtualCharacterKeysNotSupportedInKeymanWeb
* Error_VirtualKeysNotValidForMnemonicLayouts
* Warn_ExtendedShiftFlagsNotSupportedInKeymanWeb
* Hint_UnreachableKeyCode
* Error_NotSupportedInKeymanWebStore
* Warn_HelpFileMissing
* Warn_EmbedJsFileMissing
* Error_NotAnyRequiresVersion14
Given we've just run a build, this (a) seems unnecessary, and (b) seems
to go wrong in some circumstances anyway, e.g.
https://build.palaso.org/buildConfiguration/Keyman_Developer_Release/421326?buildTab=log&focusLine=19936&linesState=18839&logView=flowAware:
```
07:01:29 > @keymanapp/kmc@17.0.205-alpha prepublishOnly
07:01:29 > npm run build
07:01:29
07:01:31
07:01:31 > @keymanapp/kmc@17.0.205-alpha build
07:01:31 > tsc -b
07:01:31
07:01:35 ../../../common/web/types/build/src/kmx/kmx.d.ts(1,1): error TS1036: Statements are not allowed in ambient contexts.
07:01:35 ../../../common/web/types/build/src/kmx/kmx.d.ts(1,2): error TS1345: An expression of type 'void' cannot be tested for truthiness.
...
```
