Modern backend development can be messy. You might lock into a single runtime or server, and keeping frontend and backend types in sync is often painful. Pikku 0.6 aims to change that—offering a function-first, TypeScript-powered ecosystem that lets you build once and deploy anywhere with complete type safety.
It's been a month since our last release (with version 0.4 serving as a test), and we're excited to share the many changes and improvements in Pikku 0.5!
I'm thrilled to announce Pikku version 0.3!
This update comes shortly after version 0.2 and focuses primarily on improving the developer experience. It introduces better API validation and reduces boilerplate, making it easier and more intuitive to build powerful APIs.
We are thrilled to announce the release of pikku 0.2!
For the past few years, pikku has been quietly powering bespoke projects as a submodule. With version 0.2, we're transforming it into a fully-fledged set of libraries designed to streamline your development experience.
Before I begin, today is 20220222 as an ISO date. I had to blog something!
This article aims to explain why I went with writing Pikku instead of using nestJS. It's mostly for my sanity; since I just took a few months off of development and after returning wondered why I decided to create my own solution 😅.
So I got some great feedback on hackernews on a couple of things and wanted to write a bit more of an opinion piece.
This is a historical post from 2021. In v0.11, function signatures changed to use the wire parameter pattern, and pikkuSessionServices was renamed to pikkuWireServices. See the current documentation for updated examples.
Quick intro, Pikku is a thin wrapper ontop of express / serverless / any request-response mechanism that hides away all the boiler plate. The goal is for a user to be able to be able to add an endpoint, with schemas, permissions and session management without actually having to do any boiler plate.
Welcome to the pikku blog!
The goal is of the blog is for me to share as much as I can about some design decisions I have taken whilst working on some of my projects/ideas. Once those are open for testing I'll be providing a lot more examples!
Today I want to share a design that I have been using for maintaining state in react since the emergence of hooks.