Migrate to Typescript-go

[Bashamega]

Just a test PR, to see if this can move to Typescript-go

[saschanaz]

Seems the answer is "not yet"

[jakebailey]

First the problem is to fix this repo's imports; the repo is still using the old deprecated node10 resolution, which we did not implement in TS7.

[saschanaz]

(I want my maintainer permission to push to this PR and see how it goes 🙈)

[jakebailey]

Also, you definitely do not want to accept this PR as is, the native preview is just a preview and should not "replace" tsc at the time being. A new workflow to check it seems fine.

[jakebailey]

(I want my maintainer permission to push to this PR and see how it goes 🙈)

Me too but I haven't gotten that settled yet ☹️

[Bashamega]

The build error should be fixed when the next version of BCD is published

[Bashamega]

I have updated it to use the latest bcd and typescript syntax @jakebailey
I think the current issue is a problem with typescript-go.
It says that optionsOrLoose in semver is required. But it is actually optional:

Or is there something that I am missing?

[jakebailey]

It's using a jsconfig and then looking into the JS types for the package instead of the dts file, which is interesting. I'm not sure any of us have actually tested jsconfig.

Worth a bug and a more minimal repro.

[jakebailey]

Oh, the types for semver aren't even installed in the repo. Yeah, I think this might be expected.

[Bashamega]

I will create a minimal repro and open an issue today.
Thanks for your reply

[saschanaz]

Why did we go ahead to fix BCD instead of investigating why tsgo fails on BCD even though ts5 is okay with it?

[Bashamega]

First the problem is to fix this repo's imports; the repo is still using the old deprecated node10 resolution, which we did not implement in TS7.

I think this answers your question @saschanaz

[saschanaz]

But this PR doesn't use node10 anymore?

[jakebailey]

We didn't implement node10 in tsgo; right now it silently maps itself to bundler resolution for easier testing, but will error in the future. The errors shown in this PR (before the dep fixes) would appear with tsc in newer resolution modes.

[saschanaz]

Hmm actually, ts5 is not okay with it with node16 👀

[saschanaz]

Understood, thanks for fixing it 👍🏻

We should probably open new PR to switch from node10 and land it.

[Bashamega]

Understood, thanks for fixing it 👍🏻

We should probably open new PR to switch from node10 and land it.

I will open a separate PR for it