fix: add support for type transformations to node runner

[nwidynski]

Unfortunately I noticed this feature was only introduced on the 6th minor release of v22 & v23. We should take this into consideration properly. https://nodejs.org/en/blog/release/v22.6.0 & https://nodejs.org/en/blog/release/v23.6.0

I also learned today, that Node has feature flags, which also include one for typescript. Sorry for not checking this earlier.

[changeset-bot]

🦋 Changeset detected

Latest commit: d9bdf47

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
synckit	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/un-ts/synckit@204

commit: d9bdf47

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 4 lines in your changes missing coverage. Please review.

Project coverage is 97.41%. Comparing base (510edaa) to head (d9bdf47).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/index.ts	50.00%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #204      +/-   ##
==========================================
+ Coverage   96.26%   97.41%   +1.14%     
==========================================
  Files           1        1              
  Lines         241      232       -9     
  Branches      118      110       -8     
==========================================
- Hits          232      226       -6     
+ Misses          9        6       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nwidynski]

@JounQin I saw that you changed typeof NODE_TYPESCRIPT === 'undefined' to !NODE_TYPESCRIPT.

This is problematic because it will then also apply for supported versions if the flag isnt passed or no-experimental-strip-types is set. We only want to throw when the flag isn't present, aka in node versions prior to v22.10.

[JounQin]

@nwidynski

Are you sure?

[nwidynski]

@JounQin Yes, when running v22.10 without any flags, this value will be false. This means we are currently throwing an error. In v23.6+ this flag will be false when --no-experimental-strip-types is added, but in that case we also don't want to throw and instead filter.

[JounQin]

OK, I understand a bit now, NODE_TYPESCRIPT would be undefined on <22.10 but false on >=22.10 without any flags, right?

[JounQin]

But shouldn't we add --experimental-strip-types for Node 20.6+?

I'm going to not using this feature flag.

[nwidynski]

@JounQin Yep, the drawback of using this flag is dropping support for >=22.6 & <22.10. I think its worth it for the convenience, but I can understand wanting to support those as well.

[JounQin]

@nwidynski Please help to review https://github.com/un-ts/synckit/pull/211/files