Nuxt EdgeDB

Integrate Nuxt 3 with EdgeDB effortlessly, adding a robust database layer to your app with minimal configuration.

Features

🍱 Effortless Integration: Set up a database with just one line of configuration.
🧙 Seamless Initialization: Automates EdgeDB CLI setup and project initialization.
🎩 Live Schema Updates: Experience HMR-like DX with watchers on schema, queries, and migrations.
🛟 Typed Query Generation: Automatically generate a typed query client with @edgedb/generate.
🍩 Integrated Database Management: Pilot your database from Nuxt DevTools.
🔐 Flexible Auth: 1-line toggle Email or OAuth authentication, with support for custom auth providers.

Quick Setup

Add nuxt-edgedb-module dependency to your project

# Using pnpm
pnpm add -D nuxt-edgedb-module

# Using yarn
yarn add --dev nuxt-edgedb-module

# Using npm
npm install --save-dev nuxt-edgedb-module

Add nuxt-edgedb-module to the modules section of nuxt.config.ts

export default defineNuxtConfig({
  modules: [
    'nuxt-edgedb-module'
  ]
})

That's it! Your Nuxt project now have a database. ✨

If you do not already have EdgeDB installed on your machine, the install wizard will help you to install it.

Example project

If you want to run the example project, you have to git clone this repository and run the playground.

As EdgeDB cannot run on web containers environment like Stackblitz or CodeSandbox.

You must clone the project locally to run this playground:

git clone git@github.com:Tahul/nuxt-edgedb.git
cd nuxt-edgedb
pnpm install
pnpm stub
cd playground && pnpm run dev

Module options

You can configure any behavior from the module from your nuxt.config.ts file:

export default defineNuxtConfig({
  modules: ['nuxt-edgedb-module'],
  edgeDb: {
    // Devtools integrations
    devtools: true,
    // Completely toggle watchers feature
    watch: true,
    // Enable or disable prompts on watch events
    watchPrompt: true,
    // Generate target for your queries and query builder
    generateTarget: 'ts',
    // dbschema/ dir (you should not touch this)
    dbschemaDir: 'dbschema',
    // dbschema/ dir (you should not touch this)
    queriesDir: 'queries',
    // dbschema/ dir (you should not touch this)
    queryBuilderDir: 'dbschema/query-builder',
    // Toggles typings generation (#edgedb/interfaces)
    generateInterfaces: true,
    // Toggles typings generation (#edgedb/queries)
    generateQueries: true,
    // Toggles typings generation (#edgedb/builder)
    generateQueryBuilder: true,
    // Toggles logging messages on code generation
    generateQuiet: true,
    // Toggles project init wizard
    projectInit: true,
    // Toggle CLI install wizard
    installCli: true,
    // Toggles composables
    composables: true,
    // Toggles auto-injection on auth credentials
    injectDbCredentials: true,
    // Enables authentication intergation
    auth: false,
    // Enables oauth intergation
    oauth: false,
  }
})

Server usage

The module provides auto-imported composables available anywhere inside server/ context of your Nuxt app.

useEdgeDb

useEdgeDb exposes the raw client from edgedb import, that properly uses your Nuxt environment configuration.

// server/api/blogpost/[id].ts
import { defineEventHandler, getRouterParams } from 'h3'

export default defineEventHandler(async (req) => {
  const params = getRouterParams(req)

  const id = params.id

  const client = useEdgeDb()

  const blogpost = await client.querySingle(`
    select BlogPost {
      title,
      description
    } filter .id = ${id}
  `)

  return blogpost
})

useEdgeDbQueries

useEdgeDbQueries exposes all your queries from dbschema/queries.ts except you do not need to pass them a client.

They will use the one generated by useEdgeDb and is scoped to the current request.

// queries/getBlogPost.edgeql
select BlogPost {
  title,
  description
} filter .id = <uuid>$blogpost_id

// server/api/blogpost/[id].ts
import { defineEventHandler, getRouterParams } from 'h3'

export default defineEventHandler(async (req) => {
  const params = getRouterParams(req)

  const id = params.id

  const { getBlogpPost } = useEdgeDbQueries()

  const blogPost = await getBlogpost({ blogpost_id: id })

  return blogpost
})

You can still import queries directly from #edgedb/queries and pass them the client from useEdgeDb().

// server/api/blogpost/[id].ts
import { getBlogPost } from '#edgedb/queries'
import { defineEventHandler, getRouterParams } from 'h3'

export default defineEventHandler(async (req) => {
  const params = getRouterParams(req)

  const id = params.id

  const client = useEdgeDb()

  const blogPost = await getBlogpost(client, { blogpost_id: id })

  return blogpost
})

useEdgeDbQueryBuilder

useEdgeDbQueryBuilder exposes the generated query builder directly to your server/ context.

// server/api/blogpost/[id].ts
import { defineEventHandler, getRouterParams } from 'h3'

export default defineEventHandler(async (req) => {
  const params = getRouterParams(req)

  const id = params.id

  const client = useEdgeDb()
  const e = useEdgeDbQueryBuilder()

  const blogPostQuery = e.select(
    e.BlogPost,
    (blogPost) => ({
      id: true,
      title: true,
      description: true,
      filter_single: { id }
    })
  )

  const blogPost = await blogPostQuery.run(client)

  return blogpost
})

Typings

All the interfaces generated by EdgeDB are available throuh imports via #edgedb/interfaces.

<script setup lang="ts">
import type { BlogPost } from '#edgedb/interfaces'

defineProps<{ blogPost: BlogPost }>()
</script>

Authentification

You can use EdgeDB like a server-only database exposed via server/api endpoints and $fetch on the client, avoiding the need for authentication.

But in some projects, you might want your users to login and have an identity on the server as well, luckily, the module got you covered.

Before going through these auth installation steps, we strongly recommend you to check EdgeDB Auth documentation.

Enable `auth` option in your Nuxt configuration

export default defineNuxtConfig({
  modules: ['nuxt-edgedb-module'],
  edgedb: {
    auth: true
  }
})

Setup EdgeDB Auth in your schema

In this example, you can notice:

global current_user which defines a global property linked to the client token identity
type User is the model if your user, you are free to change it, that can be done later on thanks to migrations
access policy author_has_full_access & using (.author ?= global current_user); defines the policy for the users to only have access to their own BlogPost

// dbschema/default.esdl
using extension auth;

module default {
  global current_user := (
    assert_single((
      select User { id, name }
      filter .identity = global ext::auth::ClientTokenIdentity
    ))
  );

  type User {
    required name: str;
    required identity: ext::auth::Identity;
  }

  type BlogPost {
    property content: str {
      default := 'My blog post content.';
    };
    property title: str {
      default := 'My blog post';
    };
    required author: User;

    access policy author_has_full_access
      allow all
      using (.author ?= global current_user);

    access policy others_read_only
      allow select;
  }
}

You can edit that schema while your server is running and accept the prompt to auto-migrate.

If you are doing these edits while the server is off, you can run edgedb migration create and edgedb migrate.

Setup EdgeDB auth in your server

You will need to enable auth providers on your EdgeDB server.

That can be done through DevTools, in the EdgeDB tab.

Browse to your database, then to Auth Admin.

There, you must specify:

auth_signing_key
allowed_redirect_urls

You also must enable some providers, you can usually start with Email + Password.

If you enable required_verification, you will need to configure a SMTP server for you EdgeDB instance.

You can find further instructions on how to use Mailtrap locally to try this feature here.

Do not forget these steps must also be performed on your production environment.

Use authentication components on the client

As you enabled auth in your config, the module injected these components in your project:

You can look at the sources of these components to learn more about their props.

They all are unstyled components that only expose the logic required to achieve smooth authentication flows.

<template>
  <EdgeDbAuthEmailLogin
    v-slot="{ email, updateEmail, password, updatePassword, submit, loading }"
    redirect-to="/"
  >
    <div>
      <input
        type="email"
        :value="email"
        placeholder="your@email.com"
        @change="(e) => updateEmail(e.target.value)"
      >
      <input
        type="password"
        :value="password"
        placeholder="password"
        @change="(e) => updatePassword(e.target.value)"
      >
      <button
        type="button"
        @click="(e) => !loading && submit()"
      >
        {{ loading ? 'Loading' : 'Login' }}
      </button>
    </div>
  </EdgeDbAuthEmailLogin>
</template>

You can totally rewrite any of these components locally to implement your own authentication flows.

OAuth

If you want to use OAuth, you will have to enable it in your nuxt.config:

export default defineNuxtConfig({
  edgeDb: {
    oauth: true
  }
})

That will inject two new components to your app:

EdgeDB currently supports OAuth on following providers:

Apple
Azure (Microsoft)
GitHub
Google

In order to get OAuth working, you will have to visit your EdgeDB Instance UI, via the Nuxt DevTools.

Browse to your database and visit "Auth Admin" tab.

In your list of providers, you can then add any provider you want and configure according keys (usually client appid and secret).

Do not forget to set the callback url of your provider to the one listed at the top of your EdgeDB Auth Admin.

Once done, you can then create a simple OAuth button in your app like this:

<template>
  <!-- Gives access to all available auth providers -->
  <EdgeDbAuthProviders v-slot="{ oAuthProviders: providers }">
    <!-- Create a OAuth button behavior from a provider name -->
    <EdgeDbOAuthButton
      v-for="provider of providers"
      :key="provider.name"
      v-slot="{ redirect }"
      :provider="provider.name"
    >
      <!-- Call `redirect` from the OAuthButton -->
      <button @click="() => redirect()">
        {{ provider.display_name }}
      </button>
    </EdgeDbOAuthButton>
  </EdgeDbAuthProviders>
</template>

You will also need a call back page, that can use EdgeDbAuthCallback.

<template>
  <EdgeDbOAuthCallback
    v-slot="{ loading }"
    redirect-to="/"
  >
    <div>
      <h2>OAuth callback</h2>
      <p v-if="loading">
        Loading...
      </p>
      </UCard>
    </div>
  </EdgeDbOAuthCallback>
</template>

In just a few lines, you added a basic authentication to your application.

Client-side usage

Now that you added authentication to your project, you also have access to the useEdgeDbIdentity composable in your Nuxt app.

<script setup lang="ts">
const { isLoggedIn } = useEdgeDbIdentity()
</script>

<template>
  <div>
    <LoginButton v-if="isLoggedIn" />
    <LogoutButton v-else />
  </div>
</template>

You can look at the useEdgeDbIdentity for further usage.

Server-side usage

The authentication does use a cookie called edgedb-auth-token.

On the server, if you want to authenticate your requests to the database for the current user, you only have to pass the current request object to composables:

export default defineEventHandler(async (req) => {
  const { deleteBlogPost } = useEdgeDbQueries()

  // Will throw an error, as you cannot delete a BlogPost without being its author.
  await deleteBlogPost({ blogpost_id: id })

  const { deleteBlogPost: deleteBlogPostAuthenticated } = useEdgeDbQueries(req)

  // Succeed
  await deleteBlogPostAuthenticated({ blogpost_id: id })

  return { id }
})

Authentication environment variables

# Your EdgeDB instance auth extension base URL
NUXT_EDGEDB_AUTH_BASE_URL=http://localhost:10702/db/edgedb/ext/auth/
# Your EdgeDB instance OAuth callback URL
NUXT_EDGEDB_OAUTH_CALLBACK=http://localhost:10702/db/edgedb/ext/auth/callback
# Your app callback page
NUXT_EDGEDB_OAUTH_REDIRECT_URL=http://localhost:3000/auth/callback
# Your app app reset password URL (receiving the token from the forgot password email)
NUXT_EDGEDB_AUTH_RESET_PASSWORD_URL=http://localhost:3000/auth/reset-password
# Your app email verify url (receiving the token from email verify feature)
NUXT_EDGEDB_AUTH_VERIFY_REDIRECT_URL=http://localhost:3000/auth/verify

Going further with authentication

EdgeDB Auth only provides bare minimal identity feature for authentication.

In the code example provided for authentication setup, a User type goes along with the Identity interface.

If you want to fill User with other attributes upon user registration, you will have to implement this behavior.

The initial authentication workflow is made to be as minimal as possible so anyone can build any kind of authentication and roles system on top of it.

If you want to resolve data from OAuth providers, you can use the Nitro hook called edgedb:auth:callback from a Nitro plugin.

// server/plugins/auth.ts

export default defineNitroPlugin((app) => {
  app.hooks.hook('edgedb:auth:callback', (data) => {
    const {
      code,
      verifier,
      codeExchangeUrl,
      codeExchangeResponseData,
    } = data

    // codeExchangeResponseData contains the OAuth token from the provider.
    // ... implement your own authentication logic.
  })
})

Production

If you want to get out of development and deploy your database to prodution, you must follow EdgeDB guides.

EdgeDB is an open-source database that is designed to be self-hosted.

However, they also offer a Cloud, which is fully compatible with this module thanks to environment variables.

If you want to customize the [DSN] used by the composables, you can use the environment variables provided by the module:

NUXT_EDGEDB_HOST=
NUXT_EDGEDB_PORT=
NUXT_EDGEDB_USER=
NUXT_EDGEDB_PASS=
NUXT_EDGEDB_DATABASE=

If you want to use the env variables, you have to specify ALL of them, otherwise the client will fallback on default values.

Q&A

Will my database client be exposed in userland?

No, useEdgeDb and useEdgeDbQueries are only available in server/ context of Nuxt.

You can, as an opt-in feature, import queries from @dbschema/queries on the client.

You will need to provide these queries with a client from createClient().

<script setup lang="ts">
import { createClient } from 'edgedb'
import { getUser } from '@dbschema/queries'

const client = createClient()

const user = await getUser(client, 42)
</script>

You can also, still as an opt-in feature, import the query builder to the client.

I guess that can be useful for a super-admin/internal dashboard, but use it at your own risks in terms of security access.

<script setup lang="ts">
import e, { type $infer } from '#edgedb/builder'

const query = e.select(e.Movie, () => ({ id: true, title: true }))
type result = $infer<typeof query>
//   ^ { id: string; title: string }[]
</script>

Be careful with these imports, as if you import wrong queries, you might end up with write operations available to the client, potentially exposing your database.

How do I run my migrations in production?

Clone your Nuxt project on your production environment
Ensure you have EdgeDB CLI installed on the server
Add edgedb migrate --quiet to your CLI script

Should I version generated files?

No, as they are generated with your Nuxt client, you should add them to your .gitignore

**/*.edgeql.ts
dbschema/queries.*
dbschema/query-builder
dbschema/interfaces.ts
queries/*.query.ts

You must change these paths accordingly if you change the **Dir options.

Is HMR for my database schema really safe?

Well, it depends on when you want to use it.

I would suggest keeping watchPrompt enabled while you casually dev on your project.

That will prevent from running any unwanted migration, and will only prompt when you add new things to your schemas.

If you want to go fast and know what you are doing, you can set watchPrompt to false, and profit from automatic migration creation and applying on any change on your schemas.

If you do not want any of these features, just set watch to false and you are free to feel safe about changes applied to your development database.

HMR on your database obviously has NO effect in production context.

Why the name isn't `nuxt-edgedb`

Because that handle is already taken on NPM.

It seem to be taken by ohmree, but the package seem inactive.

If anyone happens to know him, I would be happy to get in contact!

Contributions

There is still plenty of great features to build for this integration.

I would be happy to receive and review any Pull Request.

Development

# Install dependencies
npm install

# Generate type stubs
npm run dev:prepare

# Develop with the playground
npm run dev

# Build the playground
npm run dev:build

# Run ESLint
npm run lint

# Run Vitest
npm run test
npm run test:watch

# Release new version
npm run release

Name		Name	Last commit message	Last commit date
Latest commit History 41 Commits
.github		.github
.vscode		.vscode
minimal-starter		minimal-starter
playground		playground
src		src
test		test
.editorconfig		.editorconfig
.gitignore		.gitignore
.npmrc		.npmrc
CHANGELOG.md		CHANGELOG.md
README.md		README.md
build.config.ts		build.config.ts
eslint.config.js		eslint.config.js
package.json		package.json
pnpm-lock.yaml		pnpm-lock.yaml
pnpm-workspace.yaml		pnpm-workspace.yaml
tsconfig.json		tsconfig.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Nuxt EdgeDB

Features

Quick Setup

Example project

Module options

Server usage

useEdgeDb

useEdgeDbQueries

useEdgeDbQueryBuilder

Typings

Authentification

Enable `auth` option in your Nuxt configuration

Setup EdgeDB Auth in your schema

Setup EdgeDB auth in your server

Use authentication components on the client

OAuth

Client-side usage

Server-side usage

Other authentication solutions

Authentication environment variables

Going further with authentication

Production

Q&A

Will my database client be exposed in userland?

How do I run my migrations in production?

Should I version generated files?

Is HMR for my database schema really safe?

Why the name isn't `nuxt-edgedb`

Contributions

Development

Sponsors

About

Releases

Packages

Languages

LeCoupa/nuxt-edgedb

Folders and files

Latest commit

History

Repository files navigation

Nuxt EdgeDB

Features

Quick Setup

Example project

Module options

Server usage

useEdgeDb

useEdgeDbQueries

useEdgeDbQueryBuilder

Typings

Authentification

Enable auth option in your Nuxt configuration

Setup EdgeDB Auth in your schema

Setup EdgeDB auth in your server

Use authentication components on the client

OAuth

Client-side usage

Server-side usage

Other authentication solutions

Authentication environment variables

Going further with authentication

Production

Q&A

Will my database client be exposed in userland?

How do I run my migrations in production?

Should I version generated files?

Is HMR for my database schema really safe?

Why the name isn't nuxt-edgedb

Contributions

Development

Sponsors

About

Resources

Stars

Watchers

Forks

Releases

Packages 0

Languages

Enable `auth` option in your Nuxt configuration

Why the name isn't `nuxt-edgedb`

Packages