As aself hosted runner administrator i want so know why my runners are crashing. If this is related to k8s, a stack trace often does help to pin down the origin of the issue.

Therefore, this change does improve the debug capability of the k8s hook implementation by providing a stack trace via the debug output if an exception happend.

Before the change

After the change

Change summary

The primary change is to enable a correctsourceMap output for the code, so the stack trace will show up the.ts origin with the correct line number of the trace and not some location within the minified / bakedindex.js.

• The linkage between thepackages/hooklib and thepackages/k8s andpackages/docker was changed from a JS based include into a TypeScript composite build. To make this happen, thebaseUrl &rootUrl required adaptation.
• The build by using a combination oftsc followed byncc was replaced with a direct call ofncc due to otherwise the line number reference got lost.
• There where some type inconsistencies that pop up within thek8s/package.json that appear now due to the linkage is happening now on a typed based linkage. I guess there was also a bug within themainContainerContextPorts[port.containerPort] assignment.
• ncc andtypescript library update was required due to the used version caused a bug.