Add references to possible discussions about upstreaming this

[voxpelli]

For someone who haven't followed the history of tsd it would be neat to have it documented here why these methods hasn't been exposed upstream – if there's eg. an opposition from the TypeScript team to them or if there's something else blocking it.

I guess long term goal is to not have to maintain a fork like this?

(Also: Sorry for jumping on here with an issue this quickly, I understand it might be premature, not trying to stress you out or anything, just want to be helpful 🙂)

[SamVerschueren]

Hi @voxpelli! No worries, I would be definitely up for it to have this exposed upstream.

Working on automating the build/release process to have a cronjob run every couple of hours checking if we need to release a new version. This would make it much easier for tsd to follow the TypeScript release cycle. But it's definitely not ideal, because it requires a separate typescript dependency. Although this is actually a drop-in replacement for typescript, people will probably not use it like that.

[skarab42]

Hello @SamVerschueren @voxpelli

I would also like to see these methods exposed by TypeScript directly and I'm not sure why they aren't. For several reasons, but in particular because I needed a solution that mixed tsd-typescript and byots quickly I developed my own solution unleashed-typescript I do not maintain a TypeScript fork. Instead I use the user installed package, make a copy, patch it and export it back.

[voxpelli]

One of these methods will become official in 3.4: microsoft/TypeScript#56448

And to answer my own question I asked in the start of this issue: This is the thread that discusses exposing these methods in unmodified TS: microsoft/TypeScript#9879