Skip to main content

mastodon - Link to source

w00t, just got the major refactor branch of NodeKit (github.com/small-tech/nodekit) running the Hello Count example for the first time.

Been refactoring the hell out of NodeKit recently to take it from prototype to maintainable app.

Nice to have a little win.

Now to find all the other things that are no doubt broken :)

#NodeKit #SmallTech #NodeJS #server


GitHub - small-tech/nodekit: A Small Web server.

A Small Web server. Contribute to small-tech/nodekit development by creating an account on GitHub.
GitHub
#server #SmallTech #nodejs #NodeKit
in reply to Aral Balkan

Aral Balkan
mastodon - Link to source
Aral Balkan
• •

Yay! WebSocket routes (and the simple chat example) are working again too :)

#NodeKit #SmallTech #refactor

#SmallTech #NodeKit #refactor
in reply to Aral Balkan

Endless Mason
mastodon - Link to source
Endless Mason
• •
are Websocket routes like jsonrpc?
in reply to Endless Mason

Aral Balkan
mastodon - Link to source
Aral Balkan
• •
(Although I did implement a basic RPC implementation for Domain, which I’m building on top go NodeKit. I might pull that out into the framework at some point if I find I can make it generic enough without adding undue complexity.)
in reply to Aral Balkan

Aral Balkan
mastodon - Link to source
Aral Balkan
• •
NodeKit refactor details

Besides the goal of having everything nicely encapsulated and unit tested, the major difference in this refactor is that the production and development servers have separate loader and main processes.

The prototype was a real jumble and littered with conditionals. Once I start working on the dev server I’ll likely pull out some common base functionality but my goal is to keep the production server as simple as possible.

⇧