A personal backend for personal projects
A backend TypeScript library used for common functionality in personal backend projects.
Base for personal backend projects with NestJs.
A backend TypeScript library used for common functionality in personal backend projects.
A backend TypeScript library used for common functionality in personal backend projects.
The azure module for @backstage/plugin-scaffolder-backend
Web3 module to interact with the Ethereum blockchain accounts stored in the node.
HTML5 backend for React DnD
Multi-channel AI gateway with extensible messaging integrations
i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.
ASN.1 schema for PKCS #12 personal information exchange structures defined in RFC 7292.
Amazon Cognito Identity Provider JavaScript SDK
Clerk Backend SDK - REST Client for Backend API & JWT verification utilities
Core API used by Backstage backend plugins
Use react-devtools outside of the browser
This package helps to transform resources to an i18next backend
Vanilla JavaScript backend for TensorFlow.js
The Firebase Authenticaton component of the Firebase JS SDK.
CLI to scaffold a production-ready Express.js backend instantly
GPU accelerated WebGL backend for TensorFlow.js
backend layer for i18next to chain backends
A mock backend for testing React DnD apps
Multi Backend system compatible with DnD Core / React DnD
Library used in the fieldnote personal content management system. I wrote this library to assist in accessing extended attributes from support operating systems and then transferring them, despite the git backend, to the fieldnote server. Once there they are stored in a redis database for further manipulation.
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace