PABLOF7z on Nostr: PSA: NDK has moved to a monorepo structure. This will hopefully mean that I will be ...
PSA:
NDK has moved to a monorepo structure.
This will hopefully mean that I will be able to REALLY pick up the pace in deploying new features and sibling ndk-* packages (like ndk-svelte, ndk-svelte-components, ndk-cache-redis, etc)
Why?
The way I develop NDK is usually as a byproduct of other software I build, but I always have to backport my generic code that would benefit of being part of NDK or an NDK-related package.
That small friction, because I'm lazy, means that sometimes it takes me months to release very useful code (as was the case with ndk-svelte) just because I don't get around to extracting it from my codebases.
No more!
The intent is that now I'll be able to write any NDK code I'm writing in my software directly in NDK and, when ready, release it. No backporting needed.
# TL;DR
Expect a lot more frequent releases of ndk and ndk-related projects
LFG!
NDK has moved to a monorepo structure.
This will hopefully mean that I will be able to REALLY pick up the pace in deploying new features and sibling ndk-* packages (like ndk-svelte, ndk-svelte-components, ndk-cache-redis, etc)
Why?
The way I develop NDK is usually as a byproduct of other software I build, but I always have to backport my generic code that would benefit of being part of NDK or an NDK-related package.
That small friction, because I'm lazy, means that sometimes it takes me months to release very useful code (as was the case with ndk-svelte) just because I don't get around to extracting it from my codebases.
No more!
The intent is that now I'll be able to write any NDK code I'm writing in my software directly in NDK and, when ready, release it. No backporting needed.
# TL;DR
Expect a lot more frequent releases of ndk and ndk-related projects
LFG!