fix: wrong line number in stack trace

[ANGkeith]

npm uninstall ts-node source-map-support @types/source-map-support
npm install --save-dev tsx

Issue

Using the following

# .gitlab-ci.yaml
---
job:
  image: test-err
  script:
    - echo 1

The stack trace returns the wrong line number.

which is possibly related to https://www.github.com/TypeStrong/ts-node/issues/2053, thus replacing ts-node with tsx

[firecow]

merge with master please @ANGkeith

[firecow]

@ANGkeith We need to ensure that stack traces in the pkg binaries still works, when you remove the sourcemap package.

[ANGkeith]

opps, forgot about that..

but do we really need sourcemap for the binary ?

i thought sourcemap is more for dev/debugging

[ANGkeith]

anyways,

@ANGkeith We need to ensure that stack traces in the pkg binaries still works, when you remove the sourcemap package.

should be fixed already

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[firecow]

@ANGkeith We don't have any security concerns going on in this tool, so I can't think of a reason why we would want to exclude such epic piece of debug information, when users make bug reports.