When will it be released to NPM?

[rxliuli]

Well, it seems a bit troublesome to try it out right now. Maybe publishing it on NPM would attract more people to use it?

[jakebailey]

Publishing compiled binaries for all of the different platforms with signing is its own challenge; it's probably too early at this moment to do it, but we will certainly need to do so in the future.

[rxliuli]

Can I create a PR for this? Just like tools like esbuild do, it requires some steps, but it's feasible. Maybe I'll create a repo to test it out first.

[RyanCavanaugh]

We'd really like to be in more of a "We think this will build your (arbitrary) project correctly" state before putting it on npm. The barrier of having people build themselves is intentional as part of setting expectations.

[rxliuli]

Okay, then I will temporarily release an unofficial version for those interested in testing the performance improvements quickly.

https://github.com/rxliuli/tsgo-npm-release

[JeanMeche]

From a security point of view, this is probably a bad idea.

I'm not saying you have bad intentions but you could.

[jakebailey]

Yes, for both of you doing this now, be sure to mention how unofficial it is; I'm sure you have good intentions, but people should really not be running random downloaded binaries without them coming from official sources.

[sxzz]

Of course, binary safety concerns exist, so unlike directly uploading to npm, my distribution is built using GitHub Actions, with all source code made publicly available. If concerns remain, users can simply fork the repository and trigger the build job themselves.

[sxzz]

I have started hosting pre-built binaries on the more distributed GitHub Releases at https://github.com/sxzz/tsgo-releases, with daily builds automated through GitHub Actions.

If the official team has any questions or concerns, please let me know.

[Zaid-maker]

That's amazing