A CLI tool to quickly setup an Express.js backend in TypeScript, using essential configurations and user's preferences.
Common TypeScript types used within Backstage
Types and validators that help describe the model of a Backstage Catalog
GitHub backend for Decap CMS
Query result type converters for node-postgres
Clerk Backend SDK - REST Client for Backend API & JWT verification utilities
This package contains types and schema definitions for the n8n internal API, so that these can be shared between the backend and the frontend code.
The plugin-events-node module for @backstage/plugin-events-backend
Build, Validate, Route, Authenticate and Mock using OpenAPI definitions. Framework-agnostic
The Backstage backend plugin that helps you create new things
Common functionalities for the scaffolder, to be shared between scaffolder and scaffolder-backend plugin
The Backstage backend plugin that provides the Backstage catalog
A library for Backstage backend plugins that want to interact with the search backend plugin
Common functionalities for kubernetes, to be shared between kubernetes and kubernetes-backend plugin
CLI to scaffold a production-ready Express.js backend instantly
This package is the entry point for customers to define their Amplify backend using `defineBackend`. It also pulls in functions for defining other feature verticals.
This package contains shared types used to define the contracts between DevCycle SDKs and backend APIs.
OAuth 2.0 authorization server toolkit for Node.js.
Common typings for the Stoplight ecosystem.
Shared type definitions for the Node Slack SDK
GitHub backend for Netlify CMS
JavaScript SDK for Base44 API
HTML5 backend for React DnD
translation addon for qvac
This gem implements flexible time-ordered activity feeds commonly used withing social networking applications. As events occur, they are pushed into the Feed and distributed to all users that need to see the event. Upon the user visiting their "feed page", a pre-populated ordered list of events is returned by the library. Typically the data stored in the feed is a short-hand condensed variant of models, but it can also be a fully Marshalled objects, or JSON serializations.
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