Anyone fluent with tree sitter grammars (and/or LSPs) want to help me with implementing NodeKit (https://github.com/small-tech/nodekit) code intelligence for Helix editor?
Phew, finally merged my “major refactor” NodeKit branch into main. The previous main branch is now archived in the prototype branch.
Only production mode is functional right now but it’s a maintainable codebase (not like the jumble the prototype was as I was working to get things working for the first time).
Also: So. Little. Code. 😍
Now to add more tests and the development mode server functionality as I go.
Yay, progress! 👍
w00t, just got the major refactor branch of NodeKit (https://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 :)
Yesterday’s NodeKit demo made me realise how much I want some sort of hot module reloading in NodeKit sooner rather than later. So, first step, you gotta map your dependencies… ;)
✅ Step 1
If you want to play with it yourself, I just checked in the code here:
Introducing the NodeKit for Codium extension.
By the way, when I say that’s all the code. I mean that’s ALL the code in the whole project:
Run `nodekit` on that folder, get the result in the browser.
No scaffolding. No configuration. No bundlers.
I make small things.
This is my personal Mastodon.