This is a project to make the supabase REST API available from PrismaClient.

Overview

npm version lerna--lite CI codecov

sb-prisma

πŸ”§ This project is experimental and not yet stable, so please use with caution. We look forward to your contributions.

⚠️ For non-node runtimes such as browsers and edge workers. We do not recommend using this library if you have a choice of node.

About The Project

This is a library that uses REST API of supabase directly from the Prisma client to process databases.
Prisma is a very useful library, but it cannot be used with non-Node runtimes such as browsers or edge workers; using Prisma Cloud Data Proxy solves this problem, but it does cause delays due to cold starts and round trips.
Also, if you use subapabse-js without Prisma, you can process the database regardless of runtime, but you will throw away the very good types of Prisma clients.
This project retains the type benefits of the Prisma client, but allows runtime-independent data access by using subabase's REST API.

Install & Setup

  1. Install @sb-prisma/client
# npm
npm install @sb-prisma/client

# yarn
yarn add @sb-prisma/client
  1. Add the sb-prisma generator to your schema.prisma
generator sb {
  provider = "sb-prisma"
}

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["dataProxy"] // must specify dataProxy
}
  1. Run PRISMA_CLIENT_ENGINE_TYPE=dataproxy npx prisma generate or PRISMA_CLIENT_ENGINE_TYPE=dataproxy yarn prisma generate to generate your initialize code.

This library is based on the Data Proxy client. Therefore, please set the environment variable PRISMA_CLIENT_ENGINE_TYPE to dataproxy. It is recommended to register it as an alias in the scripts of package.json.

{
  "generate": "PRISMA_CLIENT_ENGINE_TYPE=proxy npx prisma generate"
}

Usage

Simply create the middleware with makeMiddleware and set it with .$use(). Now, before the prisma client communicates with the DB, it will intercept it and proxy to the REST API of supabase.

import { PrismaClient } from '@prisma/client'
import { makeMiddleware } from '@sb-prisma/client'

const db = new PrismaClient()
const sbMiddleware = makeMiddleware(
  process.env.SUPABASE_URL ?? '',
  process.env.SUPABASE_ANON_KEY ?? '',
)
db.$use(sbMiddleware)

const main = async () => {
  const users = await db.user.findMany({
    select: {
      id: true,
      name: true,
      email: true,
      Team: true
    },
    where: {
      age: { gte: 20 },
      OR: [
        { email: { startsWith: 'foo', mode: 'insensitive' } },
        { name: { contains: 'bar', mode: 'insensitive' } },
      ]
    },
    take: 10,
    orderBy: { name: 'asc' }
  })
  console.log(users)

  return users
}

main()

Supported APIs

See APIs.md

Contribution

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

License

This project is licensed under the MIT License - see the LICENSE file for details


This generator was bootstraped using create-prisma-generator

Comments
  • The automated release is failing 🚨

    The automated release is failing 🚨

    :rotating_light: The automated release from the main branch failed. :rotating_light:

    I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

    You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this πŸ’ͺ.

    Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

    Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

    If you are not sure how to resolve this, here are some links that can help you:

    If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.


    Invalid npm token.

    The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

    If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default " Authorization and writes" level.

    Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.


    Good luck with your project ✨

    Your semantic-release bot :package::rocket:

    semantic-release 
    opened by github-actions[bot] 4
  • chore(deps-dev): bump @types/node from 17.0.31 to 17.0.36 in /packages/generator

    chore(deps-dev): bump @types/node from 17.0.31 to 17.0.36 in /packages/generator

    Bumps @types/node from 17.0.31 to 17.0.36.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps-dev): bump typescript from 4.6.4 to 4.7.2 in /packages/generator

    chore(deps-dev): bump typescript from 4.6.4 to 4.7.2 in /packages/generator

    Bumps typescript from 4.6.4 to 4.7.2.

    Release notes

    Sourced from typescript's releases.

    TypeScript 4.7.2

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7 RC

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7 Beta

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps-dev): bump prisma from 3.13.0 to 3.14.0 in /packages/generator

    chore(deps-dev): bump prisma from 3.13.0 to 3.14.0 in /packages/generator

    Bumps prisma from 3.13.0 to 3.14.0.

    Release notes

    Sourced from prisma's releases.

    3.14.0

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    CockroachDB connector is now Generally Available!

    We are proud to announce the CockroachDB connector is now stable and Generally Available. The connector was built in joined efforts with the team at Cockroach Labs and comes with full Prisma Client and Prisma Migrate support.

    If you're upgrading from Prisma version 3.9.0+ or the PostgreSQL connector, you can now run npx prisma db pull and review the changes to your schema. To learn more about CockroachDB-specific native types we support, refer to our docs.

    To learn more about the connector and how it differs from PostgreSQL, head to our documentation.

    PostgreSQL GIN, GiST, SP-GiST, and BRIN indexes support (Preview)

    We introduced the extendedIndexes Preview feature in version 3.5.0, and we have been adding new configuration options for indexes. We've expanded index type support with the GIN, GiST, SP-GiST, and BRIN indexes in this release.

    To make use of an index type, you can update your Prisma schema by providing the type argument to the @@index attribute:

    datasource db {
      provider = "postgresql"
      url      = env("DATABASE_URL")
    }
    

    generator client { provider = "prisma-client-js" previewFeatures = ["extendedIndexes"] }

    model Post { id Int @​id title String content String? tags Json?

    @@​index([tags], type: Gin) }

    The following SQL will be generated in your migration when you run prisma migrate dev:

    CREATE TABLE "Post" (
        "id" INTEGER NOT NULL,
        "title" TEXT NOT NULL,
        "content" TEXT,
        "tags" JSONB,
        CONSTRAINT "Post_pkey" PRIMARY KEY ("id")
    );
    

    CREATE INDEX "Post_tags_idx" ON "Post" USING GIN ("tags"); </tr></table>

    ... (truncated)

    Commits
    • c896178 chore(deps): update engines to 3.14.0-36.2b0c12756921c891fec4f68d9444e18c7d5d...
    • 7c32ecc chore(deps): update engines to 3.14.0-35.b139d939b80290fb7fb7a0455a577fcf02fa...
    • 197f919 fix(client): Fix package path in generate output (#13031)
    • 9bc80fb chore(deps): update engines to 3.14.0-34.5cf26752c9aac4cf41ddca31b999a4a4906f...
    • 8b663d2 chore(deps): update engines to 3.14.0-33.656da0566481bafc47a8a1f135ab368779db...
    • f67fe45 chore(deps): update jest
    • 4ae6ae9 chore(deps): update engines to 3.14.0-32.13d12f1fc9655c2d6bbd8f772677f0dc1e66...
    • 9b3eb5b chore(deps): update engines to 3.14.0-31.bdec961782f52c38a7daf86dc155e89e6405...
    • b856420 chore(deps): update engines to 3.14.0-30.17e2b313119d2b13299393860d690564a3ec...
    • aff1b11 chore(deps): update engines to 3.14.0-28.7065cb28b6b34148da7ce0e72533104aab97...
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps-dev): bump ts-jest from 28.0.1 to 28.0.2 in /packages/generator

    chore(deps-dev): bump ts-jest from 28.0.1 to 28.0.2 in /packages/generator

    Bumps ts-jest from 28.0.1 to 28.0.2.

    Changelog

    Sourced from ts-jest's changelog.

    28.0.2 (2022-05-07)

    Bug Fixes

    • transformers: use Array.sort in hoisting transformer (#3498) (e400a6e), closes #3476
    Commits
    • aefc5f4 chore(release): 28.0.2 (#3501)
    • 966ca95 build(deps-dev): bump eslint from 8.14.0 to 8.15.0 (#3500)
    • 12d906d build(deps-dev): bump @​types/react from 18.0.8 to 18.0.9 (#3499)
    • e400a6e fix(transformers): use Array.sort in hoisting transformer (#3498)
    • 8e1e8dd build(deps-dev): bump @​types/jest from 27.4.1 to 27.5.0
    • See full diff in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 2
  • chore(deps-dev): bump @types/node from 17.0.31 to 18.0.0 in /packages/generator

    chore(deps-dev): bump @types/node from 17.0.31 to 18.0.0 in /packages/generator

    Bumps @types/node from 17.0.31 to 18.0.0.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps-dev): bump prisma from 3.13.0 to 3.15.2 in /packages/generator

    chore(deps-dev): bump prisma from 3.13.0 to 3.15.2 in /packages/generator

    Bumps prisma from 3.13.0 to 3.15.2.

    Release notes

    Sourced from prisma's releases.

    3.15.2

    Today, we are issuing theΒ 3.15.2 patch release.

    Fixes

    In order to use the Prisma Data Proxy via Prisma Client, you need to generate it with prisma generate --data-proxy as described in our documentation. We are introducing PRISMA_GENERATE_DATAPROXY="true" as an additional way to do the same thing, but via an environment variable.

    This is necessary, for example, to reliably deploy a Prisma Client for Data Proxy on Vercel Serverless Functions, where it can be hard to update the build command to run prisma generate --data-proxy. Starting with this version you can just set PRISMA_GENERATE_DATAPROXY="true" as an environment variable the Vercel project settings.

    If you are unfamiliar with the Data Proxy, read how to get started.

    3.15.1

    Today, we are issuing the 3.15.1 patch release.

    Fixes

    3.15.0

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Improvements to Prisma Client for Data Proxy

    In this release, we're shipping a couple of improvements to Prisma Client for Data Proxy.

    The Prisma Data Proxy provides connection management and pooling for database connections for efficiently scaling database connections in serverless environments. The Prisma Client for Data Proxy provides support for connecting to the Prisma Data Proxy using HTTP.

    We introduced this feature in version 3.3.0 and constantly shipped features, fixes, and improvements.

    One of the changes in this release is improving the Prisma Client for the Data Proxy generation step.

    datasource db {
      provider = "postgresql"
      url      = env("DATABASE_URL")
    }
    

    generator client { provider = "prisma-client-js"

    • previewFeatures = ["dataProxy"] }

You can generate Prisma Client for the Data Proxy it by using the --data-proxy flag:

npx prisma generate --data-proxy

... (truncated)

Commits
  • 5eaac27 rename env var for data proxy generate
  • 30da823 fix(client, cli): patch for data proxy fixes (#13835)
  • 13422dd fix: bump engines to 3.15.1-1.461d6a05159055555eb7dfb337c9fb271cbd4d7e
  • a7b02ca chore(client, cli): implement --data-proxy [DPGA, 1] (#13561)
  • 5f64b0d chore(deps): update engines to 3.15.0-29.b9297dc3a59307060c1c39d7e4f5765066f3...
  • 37c031e chore(deps): update studio to v0.462.0
  • a4c5044 chore(deps): update engines to 3.15.0-28.436b66b7726f12400ec41433029e49d8c97f...
  • 74f1bf8 feat(client): Expose metrics to the client (#13584)
  • 7cb98ac chore(deps): update engines to 3.15.0-25.85b689a79df86c0da0e3676d1c001c946c2d...
  • 3c8abed chore(deps): update engines to 3.15.0-24.756a5f87dde7040808cfdb6a84c09bc6d0fa...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependencies 
opened by dependabot[bot] 1
  • chore(deps): bump @prisma/generator-helper from 3.13.0 to 3.15.2 in /packages/generator

    chore(deps): bump @prisma/generator-helper from 3.13.0 to 3.15.2 in /packages/generator

    Bumps @prisma/generator-helper from 3.13.0 to 3.15.2.

    Release notes

    Sourced from @​prisma/generator-helper's releases.

    3.15.2

    Today, we are issuing theΒ 3.15.2 patch release.

    Fixes

    In order to use the Prisma Data Proxy via Prisma Client, you need to generate it with prisma generate --data-proxy as described in our documentation. We are introducing PRISMA_GENERATE_DATAPROXY="true" as an additional way to do the same thing, but via an environment variable.

    This is necessary, for example, to reliably deploy a Prisma Client for Data Proxy on Vercel Serverless Functions, where it can be hard to update the build command to run prisma generate --data-proxy. Starting with this version you can just set PRISMA_GENERATE_DATAPROXY="true" as an environment variable the Vercel project settings.

    If you are unfamiliar with the Data Proxy, read how to get started.

    3.15.1

    Today, we are issuing the 3.15.1 patch release.

    Fixes

    3.15.0

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Improvements to Prisma Client for Data Proxy

    In this release, we're shipping a couple of improvements to Prisma Client for Data Proxy.

    The Prisma Data Proxy provides connection management and pooling for database connections for efficiently scaling database connections in serverless environments. The Prisma Client for Data Proxy provides support for connecting to the Prisma Data Proxy using HTTP.

    We introduced this feature in version 3.3.0 and constantly shipped features, fixes, and improvements.

    One of the changes in this release is improving the Prisma Client for the Data Proxy generation step.

    datasource db {
      provider = "postgresql"
      url      = env("DATABASE_URL")
    }
    

    generator client { provider = "prisma-client-js"

    • previewFeatures = ["dataProxy"] }
  • You can generate Prisma Client for the Data Proxy it by using the --data-proxy flag:

    npx prisma generate --data-proxy
    

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump @prisma/sdk from 3.13.0 to 3.15.2 in /packages/generator

    chore(deps): bump @prisma/sdk from 3.13.0 to 3.15.2 in /packages/generator

    Bumps @prisma/sdk from 3.13.0 to 3.15.2.

    Release notes

    Sourced from @​prisma/sdk's releases.

    3.15.2

    Today, we are issuing theΒ 3.15.2 patch release.

    Fixes

    In order to use the Prisma Data Proxy via Prisma Client, you need to generate it with prisma generate --data-proxy as described in our documentation. We are introducing PRISMA_GENERATE_DATAPROXY="true" as an additional way to do the same thing, but via an environment variable.

    This is necessary, for example, to reliably deploy a Prisma Client for Data Proxy on Vercel Serverless Functions, where it can be hard to update the build command to run prisma generate --data-proxy. Starting with this version you can just set PRISMA_GENERATE_DATAPROXY="true" as an environment variable the Vercel project settings.

    If you are unfamiliar with the Data Proxy, read how to get started.

    3.15.1

    Today, we are issuing the 3.15.1 patch release.

    Fixes

    3.15.0

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Improvements to Prisma Client for Data Proxy

    In this release, we're shipping a couple of improvements to Prisma Client for Data Proxy.

    The Prisma Data Proxy provides connection management and pooling for database connections for efficiently scaling database connections in serverless environments. The Prisma Client for Data Proxy provides support for connecting to the Prisma Data Proxy using HTTP.

    We introduced this feature in version 3.3.0 and constantly shipped features, fixes, and improvements.

    One of the changes in this release is improving the Prisma Client for the Data Proxy generation step.

    datasource db {
      provider = "postgresql"
      url      = env("DATABASE_URL")
    }
    

    generator client { provider = "prisma-client-js"

    • previewFeatures = ["dataProxy"] }
  • You can generate Prisma Client for the Data Proxy it by using the --data-proxy flag:

    npx prisma generate --data-proxy
    

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    dependencies 
    opened by dependabot[bot] 1
  • chore(deps-dev): bump @types/node from 17.0.31 to 17.0.40 in /packages/generator

    chore(deps-dev): bump @types/node from 17.0.31 to 17.0.40 in /packages/generator

    Bumps @types/node from 17.0.31 to 17.0.40.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps-dev): bump typescript from 4.6.4 to 4.7.3 in /packages/generator

    chore(deps-dev): bump typescript from 4.6.4 to 4.7.3 in /packages/generator

    Bumps typescript from 4.6.4 to 4.7.3.

    Release notes

    Sourced from typescript's releases.

    TypeScript 4.7.3

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7.2

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7 RC

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7 Beta

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump @prisma/generator-helper from 3.13.0 to 4.0.0 in /packages/generator

    chore(deps): bump @prisma/generator-helper from 3.13.0 to 4.0.0 in /packages/generator

    Bumps @prisma/generator-helper from 3.13.0 to 4.0.0.

    Release notes

    Sourced from @​prisma/generator-helper's releases.

    4.0.0

    We're excited to share the 4.0.0 stable release today. πŸŽ‰

    Prisma 4.0.0 features a variety of improvements across Prisma Migrate, Prisma schema, and Prisma Client. These changes will impact most Prisma users, particularly those who used some of our most popular Preview features around advanced index management, raw SQL queries, and filtering rows by properties of JSON.

    As this is a major release, we included many breaking bug fixes and other enhancements, but we believe upgrading is worthwhile. You can learn about upgrading in our Prisma 4 Upgrade guide.

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Here's a TL;DR:

    • Preview features moved to General Availability
      • extendedIndexes
      • filterJson
      • improvedQueryRaw
    • Improvements to the Prisma Schema
      • Defaults values for scalar lists (arrays)
      • Improved default support for embedded documents in MongoDB
      • Explicit unique constraints for 1:1 relations
      • Removed support for usage of references on implicit m:n relations
      • Enforcing uniqueness of referenced fields in the references argument in 1:1 and 1:m relations for MySQL
      • Removal of undocumented support for the type alias
      • Removal of the sqlite protocol for SQLite URLs
      • Better grammar for string literals
    • New Prisma Client APIs
      • findUniqueOrThrow
      • findFirstOrThrow
    • General improvements
      • Deprecating rejectOnNotFound
      • Fix rounding errors on big numbers in SQLite
      • DbNull, JsonNull, and AnyNull are now objects
      • Prisma Studio updates
      • Dropped support for Node 12
      • New default sizes for statement cache
      • Renaming of @prisma/sdk npm package to @prisma/internals
      • Removal of the internal schema property from the generated Prisma Client

    extendedIndexes is now Generally Available

    Starting with this release, we're excited to announce that extendedIndexes is now Generally Available! πŸš€

     generator client {
       provider        = "prisma-client-js"
    -  previewFeatures = ["extendedIndexes"]
     }
    

    We introduced extendedIndexes in 3.5.0 and have constantly been shipping improvements in the subsequent releases to the configuration of indexes.

    ... (truncated)

    Commits
    • da4538d fix(client): support list defaults in DMMF types (#13984)
    • df2b10e chore(deps): update devdependencies (non-major)
    • eb7d587 chore(deps): update dependency @​types/jest to v28.1.3
    • 88fe98a chore: added internal disclaimer for Prisma 4 (#13874)
    • 9bd2d4f chore(deps): update devdependencies (non-major) (#13821)
    • 0f5dc6a chore(deps): update devdependencies (non-major) (#13591)
    • 5aec1cc chore(deps): update jest (#13684)
    • 3b74be7 chore(deps): update definitelytyped (#13398)
    • a7b02ca chore(client, cli): implement --data-proxy [DPGA, 1] (#13561)
    • fbd24a3 chore(deps): update dependency @​types/jest to v28
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps-dev): bump prisma from 3.13.0 to 4.0.0 in /packages/generator

    chore(deps-dev): bump prisma from 3.13.0 to 4.0.0 in /packages/generator

    Bumps prisma from 3.13.0 to 4.0.0.

    Release notes

    Sourced from prisma's releases.

    4.0.0

    We're excited to share the 4.0.0 stable release today. πŸŽ‰

    Prisma 4.0.0 features a variety of improvements across Prisma Migrate, Prisma schema, and Prisma Client. These changes will impact most Prisma users, particularly those who used some of our most popular Preview features around advanced index management, raw SQL queries, and filtering rows by properties of JSON.

    As this is a major release, we included many breaking bug fixes and other enhancements, but we believe upgrading is worthwhile. You can learn about upgrading in our Prisma 4 Upgrade guide.

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Here's a TL;DR:

    • Preview features moved to General Availability
      • extendedIndexes
      • filterJson
      • improvedQueryRaw
    • Improvements to the Prisma Schema
      • Defaults values for scalar lists (arrays)
      • Improved default support for embedded documents in MongoDB
      • Explicit unique constraints for 1:1 relations
      • Removed support for usage of references on implicit m:n relations
      • Enforcing uniqueness of referenced fields in the references argument in 1:1 and 1:m relations for MySQL
      • Removal of undocumented support for the type alias
      • Removal of the sqlite protocol for SQLite URLs
      • Better grammar for string literals
    • New Prisma Client APIs
      • findUniqueOrThrow
      • findFirstOrThrow
    • General improvements
      • Deprecating rejectOnNotFound
      • Fix rounding errors on big numbers in SQLite
      • DbNull, JsonNull, and AnyNull are now objects
      • Prisma Studio updates
      • Dropped support for Node 12
      • New default sizes for statement cache
      • Renaming of @prisma/sdk npm package to @prisma/internals
      • Removal of the internal schema property from the generated Prisma Client

    extendedIndexes is now Generally Available

    Starting with this release, we're excited to announce that extendedIndexes is now Generally Available! πŸš€

     generator client {
       provider        = "prisma-client-js"
    -  previewFeatures = ["extendedIndexes"]
     }
    

    We introduced extendedIndexes in 3.5.0 and have constantly been shipping improvements in the subsequent releases to the configuration of indexes.

    ... (truncated)

    Commits
    • 0d6f1d1 chore(deps): update studio to 0.465.0 (#14030)
    • 6da1a84 chore: revert "fix(sdk): avoid crash in prisma version, rename 'getVersion' -...
    • fda0455 chore(deps): update engines to 3.16.0-49.da41d2bb3406da22087b849f0e911199ba4f...
    • ffb1ec4 chore(deps): update engines to 3.16.0-46.7913709f1e48160e65e366f365c239e3017a...
    • c6951ec chore(deps): update engines to 3.16.0-45.e46a8f52bc07feff72927e42c1fa8bb4627d...
    • ea51fce chore: bump Node.js requirement from 14.0.0 "Current" to 14.17.0 LTS (#13997)
    • 3718bfa fix(sdk): avoid crash in prisma version, rename 'getVersion' -> 'getBinaryVer...
    • 8e90f8a feat(sdk): improved error reporting by adding detail to getConfig and getDmmf...
    • 5e4d9c2 chore(deps): update engines to 3.16.0-44.b49ece5df25d5e0d1d4b4e8935cc70745d76...
    • 8e9f510 chore(deps): update engines to 3.16.0-43.81a0ee489e5f8c8ce98440028ea905009243...
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps-dev): bump @types/node from 17.0.31 to 18.0.1 in /packages/generator

    chore(deps-dev): bump @types/node from 17.0.31 to 18.0.1 in /packages/generator

    Bumps @types/node from 17.0.31 to 18.0.1.

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 1
  • chore(deps): bump @prisma/sdk from 3.13.0 to 4.0.0 in /packages/generator

    chore(deps): bump @prisma/sdk from 3.13.0 to 4.0.0 in /packages/generator

    Bumps @prisma/sdk from 3.13.0 to 4.0.0.

    Release notes

    Sourced from @​prisma/sdk's releases.

    4.0.0

    We're excited to share the 4.0.0 stable release today. πŸŽ‰

    Prisma 4.0.0 features a variety of improvements across Prisma Migrate, Prisma schema, and Prisma Client. These changes will impact most Prisma users, particularly those who used some of our most popular Preview features around advanced index management, raw SQL queries, and filtering rows by properties of JSON.

    As this is a major release, we included many breaking bug fixes and other enhancements, but we believe upgrading is worthwhile. You can learn about upgrading in our Prisma 4 Upgrade guide.

    🌟 Help us spread the word about Prisma by starring the repo or tweeting about the release. 🌟

    Major improvements

    Here's a TL;DR:

    • Preview features moved to General Availability
      • extendedIndexes
      • filterJson
      • improvedQueryRaw
    • Improvements to the Prisma Schema
      • Defaults values for scalar lists (arrays)
      • Improved default support for embedded documents in MongoDB
      • Explicit unique constraints for 1:1 relations
      • Removed support for usage of references on implicit m:n relations
      • Enforcing uniqueness of referenced fields in the references argument in 1:1 and 1:m relations for MySQL
      • Removal of undocumented support for the type alias
      • Removal of the sqlite protocol for SQLite URLs
      • Better grammar for string literals
    • New Prisma Client APIs
      • findUniqueOrThrow
      • findFirstOrThrow
    • General improvements
      • Deprecating rejectOnNotFound
      • Fix rounding errors on big numbers in SQLite
      • DbNull, JsonNull, and AnyNull are now objects
      • Prisma Studio updates
      • Dropped support for Node 12
      • New default sizes for statement cache
      • Renaming of @prisma/sdk npm package to @prisma/internals
      • Removal of the internal schema property from the generated Prisma Client

    extendedIndexes is now Generally Available

    Starting with this release, we're excited to announce that extendedIndexes is now Generally Available! πŸš€

     generator client {
       provider        = "prisma-client-js"
    -  previewFeatures = ["extendedIndexes"]
     }
    

    We introduced extendedIndexes in 3.5.0 and have constantly been shipping improvements in the subsequent releases to the configuration of indexes.

    ... (truncated)

    Commits
    • 6da1a84 chore: revert "fix(sdk): avoid crash in prisma version, rename 'getVersion' -...
    • fda0455 chore(deps): update engines to 3.16.0-49.da41d2bb3406da22087b849f0e911199ba4f...
    • ffb1ec4 chore(deps): update engines to 3.16.0-46.7913709f1e48160e65e366f365c239e3017a...
    • 7e7e804 internals: fixed spacing after 'Details:' (#14018)
    • c6951ec chore(deps): update engines to 3.16.0-45.e46a8f52bc07feff72927e42c1fa8bb4627d...
    • 3718bfa fix(sdk): avoid crash in prisma version, rename 'getVersion' -> 'getBinaryVer...
    • 8e90f8a feat(sdk): improved error reporting by adding detail to getConfig and getDmmf...
    • 5e4d9c2 chore(deps): update engines to 3.16.0-44.b49ece5df25d5e0d1d4b4e8935cc70745d76...
    • 8e9f510 chore(deps): update engines to 3.16.0-43.81a0ee489e5f8c8ce98440028ea905009243...
    • 857531a chore(deps): update engines to 3.16.0-42.7cd57f2ac6cbe3ad1b6126eb6814ebcefa85...
    • Additional commits viewable in compare view

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 0
  • chore(deps-dev): bump typescript from 4.6.4 to 4.7.4 in /packages/generator

    chore(deps-dev): bump typescript from 4.6.4 to 4.7.4 in /packages/generator

    Bumps typescript from 4.6.4 to 4.7.4.

    Release notes

    Sourced from typescript's releases.

    TypeScript 4.7.4

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7.3

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7.2

    For release notes, check out the release announcement.

    For the complete list of fixed issues, check out the

    Downloads are available on:

    TypeScript 4.7 RC

    For release notes, check out the release announcement.

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    dependencies 
    opened by dependabot[bot] 0
  • Releases(@sb-prisma/[email protected])
    Owner
    AijiUejima
    I'm working for an IT company in Nagoya, Japan on web development
    AijiUejima
    This is a vanilla Node.js rest API created to show that it is possible to create a rest API using only vanilla Node.js

    This is a vanilla Node.js rest API created to show that it is possible to create a rest API using only vanilla Node.js. But in most cases, I would recommend you to use something like Express in a production project for productivity purposes.

    Eduardo Dantas 7 Jul 19, 2022
    A wrapper for valorant-api, a third-party API for getting data within Valorant. Available on npm

    valorant-wrapper A wrapper for the third-party valorant-api How to Use All endpoints can be accessed off the ValAPI class. import { ValAPI } from 'val

    Aircraft Overviewer 5 Nov 7, 2022
    Example project implementing authentication, authorization, and routing with Next.js and Supabase

    Magic Link Authentication and Route Controls with Supabase and Next.js To run this project, To get started with this project, first create a new proje

    Nader Dabit 134 Dec 11, 2022
    In this project, you will learn how to pull datas from supabase to google sheets in a matter of minute

    Supabase-Googlesheet In this repo, you will see how to pull datas from your supabase project using Supabase API to a Google Sheet. No matter how many

    Jady Nekena 6 Jul 28, 2022
    API dot Open Sauced is NestJS and SupaBase powered OAS3 backend designed to remove client complexity and provide a structured graph of all @open-sauced integrations

    ?? Open Sauced Nest Supabase API ?? The path to your next Open Source contribution ?? Prerequisites In order to run the project we need the following

    TED Vortex (Teodor-Eugen DuΘ›ulescu) 13 Dec 18, 2022
    Get a desktop notification every time a new correction slot is available for your 42 project.

    42_slot_watcher A simple node.js corrections slots watcher for 42, working on Windows - MacOS - Linux. What is this I was bored of having to refresh t

    Maxime 7 Dec 20, 2022
    API and site for discovering publicly-available Desmos graphs. Not affiliated with Desmos.

    desmosearch-api API and site for discovering, cataloguing, and keeping track of publicly-available Desmos graphs. Not affiliated with Desmos. This pro

    null 4 Feb 24, 2022
    Front-End mentor project for rest maps APIπŸ˜ŠπŸ‘

    REST Countries API with color theme switcher Live | Solution | Challenge Solution for a challenge from frontendmentor.io. About The Project If you're

    Ashutosh Mohanty 3 Sep 4, 2022
    Quickly bootstrap your next TypeScript REST API project. Node 16+, auto OpenAPI, Prettier+ESLint, Jest

    REST API template with autogenerated OpenAPI Quickly bootstrap your next TypeScript REST API project with the most up to date template. Included a sam

    null 6 Oct 1, 2022
    Webb-tracker-api - James Webb Space Telescope (JWST) tracking REST API

    James Webb Telescope tracking REST API Public REST API to track JWST's current status API data source: https://www.jwst.nasa.gov/content/webbLaunch/wh

    Aslan Vatsaev 67 Nov 22, 2022
    Lolis-rest - RESTful API for lolis-api

    Lolis REST RESTful + Website for Lolis API. Introduction This is a RESTful API which will be used on Lolis API Website and Wrapper. This API uses Imgu

    Waifu.sbs 3 Aug 11, 2022
    A base API template for a REST API using express.

    express-api-template A base API template for a REST API using express. Philosophy Setting up a new project can be a long and tedious process, especial

    T3NED 6 May 29, 2022
    An Amazon Kendra REST API CDK example with an API Gateway, including authentication with AWS Cognito and AWS X-Ray Tracing

    Amazon Kendra Web Service CDK Sample Amazon Kendra has a robust JSON API for use with the AWS SDK (software development kit), but does not expose endp

    AWS Samples 8 Nov 28, 2022
    The Remix Stack for deploying to Fly with Supabase, authentication, testing, linting, formatting, etc.

    Remix Supa Fly Stack Learn more about Remix Stacks. npx create-remix --template rphlmr/supa-fly-stack What's in the stack Fly app deployment with Doc

    RaphaΓ«l Moreau 157 Jan 7, 2023
    ⚑ A blazing fast, lightweight, and open source comment system for your static website, blogs powered by Supabase

    SupaComments ⚑ A blazing fast, lightweight, and open source comment system for your static website, blogs ?? Demo You can visit the Below demo blog po

    MC Naveen 112 Dec 27, 2022
    ChatMore: A web chatapp like Whatsapp - Made in Typescript, React and Supabase

    ChatMore This project is a chatapp made in React. On the main page we can authenticate, and then add todos to the our list. The ultimate goal of this

    Ulysse 75 Jan 3, 2023
    tooldb is a (soon) massive collection of frameworks and tools. It's build on Flowbite, Next.js, Tailwind CSS and uses Supabase.

    tooldb is a (soon) massive collection of frameworks and tools. It's build on Flowbite, Next.js, Tailwind CSS and uses Supabase.

    Julian Yaman 12 Jul 14, 2022
    ⚑️ CRUDify Supabase Tables

    ⚑️ CRUDify Supabase Tables ⚑️ This is a wrapper around @supabase/supabase-js that generates CRUD actions (like Prisma) to manage tables' data. Quickst

    Batyr 6 Oct 14, 2022
    A modern uptime monitoring tool & status page based on Supabase.

    StatusBase (Supabase) Uptime monitoring tool & beautiful status pages Powered by Supabase! Free β€’ Open Source β€’ Notification View Demo Β· Report Bug Β·

    StatusBase 20 Dec 3, 2022