|
@cedarjs/api
|
Cedar believes the future is serverless and multi-client. And `@cedarjs/api` makes Cedar serverless and multi-client ready. Cedar has one API to rule them all. Your API is abstracted away from any one side of your application, so you can have as many side |
MIT |
27
greenflagged
/ 1549 total
|
|
@cedarjs/api-server
|
CedarJS's HTTP server for Serverless Functions |
MIT |
18
greenflagged
/ 1547 total
|
|
@cedarjs/auth
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1549 total
|
|
@cedarjs/auth-auth0-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1549 total
|
|
@cedarjs/auth-auth0-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1547 total
|
|
@cedarjs/auth-auth0-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1547 total
|
|
@cedarjs/auth-azure-active-directory-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-azure-active-directory-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1545 total
|
|
@cedarjs/auth-azure-active-directory-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-clerk-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1547 total
|
|
@cedarjs/auth-clerk-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-clerk-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1545 total
|
|
@cedarjs/auth-custom-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-dbauth-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-dbauth-middleware
|
```tsx filename='entry.server.tsx' import type { TagDescriptor } from '@cedarjs/web' |
MIT |
27
greenflagged
/ 1544 total
|
|
@cedarjs/auth-dbauth-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-dbauth-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-firebase-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-firebase-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-firebase-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1545 total
|
|
@cedarjs/auth-netlify-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-netlify-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1544 total
|
|
@cedarjs/auth-netlify-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1545 total
|
|
@cedarjs/auth-supabase-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1546 total
|
|
@cedarjs/auth-supabase-middleware
|
```tsx filename='entry.server.tsx' import type { TagDescriptor } from '@cedarjs/web' |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/auth-supabase-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/auth-supabase-web
|
To get started, run the setup command: |
MIT |
27
greenflagged
/ 1541 total
|
|
@cedarjs/auth-supertokens-api
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/auth-supertokens-setup
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/auth-supertokens-web
|
If you want to contribute a new auth provider integration we recommend you start by implementing it as a custom auth provider in a Cedar App first. When that works you can package it up as an npm package and publish it on your own. You can then create a P |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/babel-config
|
Cedar's Babel config. This package has been extracted out of `@cedarjs/internal`. |
MIT |
7
greenflagged
/ 1541 total
|
|
@cedarjs/cli
|
The CedarJS Command Line |
MIT |
27
greenflagged
/ 1539 total
|
|
@cedarjs/cli-data-migrate
|
Cedar's data migrations as a standalone CLI command. The utility here is mainly for Docker. |
MIT |
27
greenflagged
/ 1541 total
|
|
@cedarjs/cli-helpers
|
— |
— |
27
greenflagged
/ 1541 total
|
|
@cedarjs/cli-storybook-vite
|
This CLI package is intended to be used with the [Storybook Framework package](../../storybook/README.md). Get started as follows: |
MIT |
27
greenflagged
/ 1541 total
|
|
@cedarjs/codemods
|
Codemods to ease upgrading a CedarJS Project |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/context
|
— |
— |
27
greenflagged
/ 1541 total
|
|
@cedarjs/cookie-jar
|
Specialized cookie map, that lets you set cookies with options |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/core
|
Foundational packages and config required to build CedarJS |
MIT |
6
greenflagged
/ 1539 total
|
|
@cedarjs/eslint-config
|
— |
— |
23
greenflagged
/ 1540 total
|
|
@cedarjs/eslint-plugin
|
Custom ESLint plugins used for standalone CedarJS ESLint lint rules. These rules are ment to be consumed via the larger [`@cedarjs/eslint-config`](https://github.com/cedarjs/cedar/tree/main/packages/eslint-config). |
MIT |
27
greenflagged
/ 1541 total
|
|
@cedarjs/fastify-web
|
— |
MIT |
20
greenflagged
/ 1550 total
|
|
@cedarjs/forms
|
The form package provides a set of components and utilities for building forms in Cedar applications. |
MIT |
27
greenflagged
/ 1542 total
|
|
@cedarjs/gqlorm
|
Prisma inspired GraphQL query builder |
MIT |
9
greenflagged
/ 497 total
|
|
@cedarjs/graphql-server
|
— |
— |
15
greenflagged
/ 1542 total
|
|
@cedarjs/internal
|
— |
— |
11
greenflagged
/ 1541 total
|
|
@cedarjs/jobs
|
Provides background job scheduling and processing for CedarJS. |
MIT |
27
greenflagged
/ 1541 total
|
|
@cedarjs/mailer-core
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/mailer-handler-in-memory
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/mailer-handler-nodemailer
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/mailer-handler-resend
|
We assume you have the basic boilerplate for Cedar Mailer present. We also assume that you have signed up with [Resend](https://resend.com/) and have access to an API key. |
MIT |
27
greenflagged
/ 1539 total
|
|
@cedarjs/mailer-handler-studio
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1539 total
|
|
@cedarjs/mailer-renderer-mjml-react
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1539 total
|
|
@cedarjs/mailer-renderer-react-email
|
**WIP**: This package is still a work in progress. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/ogimage-gen
|
— |
MIT |
27
greenflagged
/ 1538 total
|
|
@cedarjs/prerender
|
— |
— |
15
greenflagged
/ 1538 total
|
|
@cedarjs/project-config
|
— |
— |
27
greenflagged
/ 1540 total
|
|
@cedarjs/realtime
|
The real-time solution for CedarJS is initially for GraphQL. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/record
|
RedwoodRecord is an ORM ([Object-Relational Mapping](https://en.wikipedia.org/wiki/Object%E2%80%93relational_mapping)) built on top of Prisma. It may be extended in the future to wrap other database access packages. |
MIT |
27
greenflagged
/ 1540 total
|
|
@cedarjs/router
|
— |
— |
27
greenflagged
/ 1538 total
|
|
@cedarjs/server-store
|
— |
— |
27
greenflagged
/ 1538 total
|
|
@cedarjs/storage
|
This package houses |
MIT |
27
greenflagged
/ 1538 total
|
|
@cedarjs/structure
|
— |
— |
27
greenflagged
/ 1539 total
|
|
@cedarjs/telemetry
|
— |
— |
27
greenflagged
/ 1539 total
|
|
@cedarjs/testing
|
— |
— |
27
greenflagged
/ 1536 total
|
|
@cedarjs/tui
|
Terminal User Interface for CedarJS. A collection of helpful functions to standardise and simplify terminal output. |
MIT |
27
greenflagged
/ 1538 total
|
|
@cedarjs/utils
|
— |
— |
8
greenflagged
/ 414 total
|
|
@cedarjs/vite
|
— |
— |
27
greenflagged
/ 1534 total
|
|
@cedarjs/web
|
— |
— |
27
greenflagged
/ 1534 total
|
|
@cedarjs/web-server
|
— |
— |
27
greenflagged
/ 1536 total
|