update

[alphaleadership]

what is the current stade of the project

[mkvlrn]

It doesn't look like there's any attention to this project any longer... It's been 3 years since the last meet?

This is definitely a biased opinion, but I believe that if more effort were put into this initiative, focusing on ease of use, seamless typescript integration, and ESM support, people (such as myself) wouldn't be so divided between node and Go.

A Go monorepo is such a beautiful, simple thing. Of course we can do outstanding monorepos in node (I use turborepo), but there are so goddamn many moving parts, from exporting/importing internal dependencies, build step, dockerizing, to deploying.

If I could just have in my src/cmd directory each "outputable" code and a simplified build step just compiles each of them down to a binary, with ALL dependencies, all without having to setup a monorepo with turborepo or nx or whatever else, and without the - pardon the word - insane configuration that is currently required... That is the dream.

I can achieve something similar using Bun. Their compiling/single-executable solution is light years ahead of this project, but it still has some weird issues.

I just want to be able to bypass all the friction when doing this with node, man. =/

[GabenGar]

There is no attention because there is no one willing to spend their free time to work on the crossroads of C++, JS and OS APIs for non-specified logic.
Your post suffers from this exact same problem as you basically want a full blown bundler from it but without all the problems of setting up one and it should "just work".
I am not sure how typescript even factors into it, since any program of worth has 3rd-party dependencies and therefore a bundling step. At the point when the bundled output is fed into exe generator there is no typescript left.

[cspotcode]

@mkvlrn Have you checked out deno compile main.ts? I'm curious how it compares to bun's implementation. I do occasionally hit inconsistencies with deno's node API support.

For anyone lurking, bun's and deno's single-file executable solutions handle Typescript and bundling automatically, and they can execute node projects. deno compile main.ts is the only command you need to build an executable from a node project, no extra bundling or compilation steps required.

[RaisinTen]

It doesn't look like there's any attention to this project any longer... It's been 3 years since the last meet?

Actually, there was an SEA meeting earlier this year at the Node.js Collaboration Summit https://youtu.be/0031xkl7aMs?si=mAFbbdt12hUgZXpC&t=260.

There is no attention because there is no one willing to spend their free time to work on the crossroads of C++, JS and OS APIs for non-specified logic.

I'm available for contracting, so I'd be happy to prioritize implementing parts of SEA that are important to your company.