@palmares/client
This is the client part of the palmares framework, you should be able to use it on any runtime
This is the client part of the palmares framework, you should be able to use it on any runtime
This is the default implementation of the logger adapter, you can create others if you want to
This is the core part of the palmares framework, palmares is a framework heavily inspired by django and nestjs core ideas
Add support for working with databases with palmares framework
This is the engine that wraps the hole drizzle interface in a way palmares can understand and have full control of
EventEmitter2 as the event emitter to palmares. With this we are able to send events inside and between servers really fast.
This is the events framework for palmares, it's responsible for handling everything that is Pub/Sub like websockets, pub/sub like redis, and other types of asynchronous background tasks
This is the adapter for express framework to work with Palmares framework
This is the jest testing adapter, we are abstracting jest to work flawlessly with palmares
Palmares logging interface so you can log it to the console or other places as well
This is the nodejs standard library, it uses the std interfaces to interact with the environment so palmares can work with the same APIs without worrying about the environment it is running on.
The default implementation for redis to act as pub/sub for palmares. It's specially useful as a layer.
This defines a default schema definition for validation of data, it abstract popular schema validation libraries like zod, yup, valibot and others"
This is the engine that wraps the hole sequelize interface in a way palmares can understand and have full control of
This package is responsible for validating incoming requests and format how the requests are sent to the user.
The server from palmares, this is what you will use generally to make HTTP requests
The palmares standard library, this is used to interact with the environment we are working with, it can be a browser, node.js, bun, deno or whatever runtime. The standard library should include interfaces that we can extend in whatever environment we are
This defines a default test framework testing stuff inside of the framework
This is the adapter for Vercel allows you to deploy Palmares apps on Vercel
Adds support for websockets on the Palmares framework