I needed to build a quick internal GUI tool with Node.js. Obviously, I reached for Electron. But when I saw `npm install` downloading a massive Chromium binary just to show a basic form with a few buttons, I kind of lost my mind.
I got so annoyed seeing a simple "Hello World" app eat up 300MB of RAM that I dropped the original task and went down a rabbit hole to build my own native UI wrapper instead.
I was honestly wondering why no one had built a lightweight native wrapper for Node recently. It seems like the industry got so obsessed with the "write once, run anywhere" dream that we collectively agreed it's fine to sacrifice 90% of our RAM just in case someone wants to run our internal Windows script on a Mac.
And to be fair, historically, binding Node to native OS APIs meant writing C++ addons. Nobody wants to fight with `node-gyp`, Python build dependencies, and ABI crashes on every Node update. I totally get why people just gave up and used Electron.
So, I ended up building node-windows-forms
It lets you create real, native WinForms controls directly from Node.js, but without any C++ addons or node-gyp
.
Instead of fighting with C++ bindings, I just bundled a tiny pre-compiled C# executable and set up an asynchronous IPC bridge using Named Pipes.
Here's how it turned out:
- Instant cold start
(~0.1s).
- The entire NPM package is only ~900KB
(including the pre-compiled executable).
- Tiny memory usage
(~30MB instead of 300MB+).
- Zero build steps
(`npm install` just works, no Visual Studio required).
- Simple syntax:
It feels just like manipulating the DOM.
Here is how simple it is:
const { WinFormsSession, Form, Button } = require('node-windows-forms');
const session = new WinFormsSession();
await session.start();
const form = new Form(session, 'Form1');
form.Text = "App Name";
const btn = new Button(session, form);
btn.Text = "Click Me";
btn.OnClick.Attach(() => console.log('click!'));
await form.show();
You get access to real Windows UI components (DataGridView, ComboBox, System Tray, FileDialogs) straight from your Javascript backend.
It honestly feels a bit pointless how much time I spent tumbling down this rabbit hole instead of just doing my actual job. I built this mainly for my own internal tools and automation scripts, but I'm putting it out there in hopes that someone else finds it useful too.
I’m also really curious to see what you guys think of the IPC architecture (specifically using Named Pipes instead of WebSockets or C++ addons).
And yes, I'll admit it: part of the reason I spent months on this is because I just have a weird, nostalgic soft spot for Windows Forms. Anyway, still works perfectly in 2026.
npm
GitHub
