@floatingpixels/supabase-nuxt 0.4.0 → 0.4.2

package/README.md

@@ -1,7 +1,9 @@
 # Supabase Nuxt
 
-![NPM Version](https://img.shields.io/npm/v/%40floatingpixels%2Fsupabase-nuxt?color=28CF8D)
-![NPM Downloads](https://img.shields.io/npm/dt/%40floatingpixels%2Fsupabase-nuxt)
+<p>
+  <a href="https://www.npmjs.com/package/@floatingpixels/supabase-nuxt"><img src="https://img.shields.io/npm/v/%40floatingpixels%2Fsupabase-nuxt.svg?style=flat&colorA=18181B&colorB=28CF8D" alt="Version"></a>
+  <a href="https://www.npmjs.com/package/@floatingpixels/supabase-nuxt"><img src="https://img.shields.io/npm/dt/%40floatingpixels%2Fsupabase-nuxt.svg?style=flat&colorA=18181B&colorB=28CF8Dt" alt="Downloads"></a>
+</p>
 
 ## Features
 
@@ -125,7 +127,7 @@ const signInWithOtp = async () => {
   const { error } = await supabase.auth.signInWithOtp({
     email: email.value,
     options: {
-      emailRedirectTo: 'http://localhost:3000/confirm',
+      emailRedirectTo: 'http://localhost:3000/welcome',
     },
   })
   if (error) console.log(error)
@@ -148,22 +150,22 @@ Once the authorization flow is triggered using the `auth` wrapper of the `useSup
 
 ### E-Mail Authentication
 
-When using e-mail authentication, a confirmation e-mail is sent to new users, and an e-mail containing a magic link is sent to existing users. For those links to work with your application, you need to adjust the e-mail templates in your Supabase settings under `Authentication -> Email Templates`. The generated links must contain a `token_hash` and `type` URL parameter, and point to the confirmation URL of your app, which is `/supabase/auth/confirm` by default. In addition you can set the URL parameter `next` to determine the route users will be forwarded to in your app when authorization is successful. If `next` is omitted, it will route to `/`. An example template looks like this:
+When using e-mail authentication, a confirmation e-mail is sent to new users, and an e-mail containing a magic link is sent to existing users. For those links to work with your application, you need to adjust the e-mail templates in your Supabase settings under `Authentication -> Email Templates`. The generated links must contain a `token_hash` and `type` URL parameter, and point to the confirmation URL of your app, which is `/auth/confirm` by default. In addition you can set the URL parameter `redirect_to` to determine the route users will be forwarded to in your app when authorization is successful. If `redirect_to` is omitted, it will route to `/`. An example template looks like this:
 
 ```html
 <h2>Confirm your signup</h2>
 
+<p>Hello {{ .Data.first_name }}</p>
 <p>Follow this link to confirm your user:</p>
 <p>
-  <a href="{{ .SiteURL }}/supabase/auth/confirm?token_hash={{ .TokenHash }}&type=email&next=/path-to-your-page"
-    >Confirm your email</a
+  <a href="{{ .SiteURL }}/supabase/auth/confirm?token_hash={{ .TokenHash }}&type=email&redirect_to={{ .RedirectTo }}>Confirm your email</a
   >
 </p>
 ```
 
-The confirmation route on your server is provided by this module, so you don't need to implement it yourself. It's available at `/supabase/auth/confirm`. It will automatically confirm the user and re-direct to the `next` route.
+The confirmation route on your server is provided by this module, so you don't need to implement it yourself. It's available at `/auth/confirm`. It will automatically confirm the user and re-direct to the `redirect_to` route.
 
-If you want to customize the confirmation route, you can do so by creating a server route to handle the request, and point to it in your Supabase e-mail template. Your custom route will receive the `token_hash` and `type` URL parameters, and the `next` URL parameter if provided. You can use the `useSupabaseClient` composable to confirm the user and re-direct to the `next` route:
+If you want to customize the confirmation route, you can do so by creating a server route to handle the request, and point to it in your Supabase e-mail template. Your custom route will receive the `token_hash` and `type` URL parameters, and the `redirect_to` URL parameter if provided. You can use the `useSupabaseClient` composable to confirm the user and re-direct to the `next` route:
 
 > ⚠️ You can use the provided confirm route at `/supabase/confirm`, the implementation of a custom route is optional!
 
@@ -175,7 +177,7 @@ export default defineEventHandler(async event => {
   const query = getQuery(event)
   const token_hash = query.token_hash as string
   const type = query.type as EmailOtpType | null
-  const next = (query.next as string) ?? '/'
+  const redirect_to = (query.redirect_to as string) ?? '/'
 
   if (!token_hash || !type) {
     throw createError({ statusMessage: 'Invalid token' })
@@ -188,20 +190,20 @@ export default defineEventHandler(async event => {
     throw createError({ statusMessage: error.message })
   }
 
-  await sendRedirect(event, next, 302)
+  await sendRedirect(event, redirect_to, 302)
 })
 ```
 
 ### OAuth Authentication
 
-When using OAuth authentication, you need to configure the OAuth provider in your Supabase settings under `Authentication -> Providers`. You can then use the `signInWithOAuth` method of the `auth` wrapper of the `useSupabaseClient` composable to initiate the authorization flow. This module provides a default callback under `/supabase/auth/callback` that you can provide to the authentication function:
+When using OAuth authentication, you need to configure the OAuth provider in your Supabase settings under `Authentication -> Providers`. You can then use the `signInWithOAuth` method of the `auth` wrapper of the `useSupabaseClient` composable to initiate the authorization flow. This module provides a default callback under `/auth/callback` that you can provide to the authentication function:
 
 ```ts [pages/login.vue]
 const signInWithOAuth = async () => {
   const { error } = await supabase.auth.signInWithOAuth({
     provider: 'github',
     options: {
-      redirectTo: 'http://<your-site-url>/supabase/auth/callback',
+      redirectTo: 'http://<your-site-url>/auth/callback',
     },
   })
   if (error) console.log(error)
@@ -210,7 +212,7 @@ const signInWithOAuth = async () => {
 
 You can customize the callback by creating your own server route, and point to it when calling `signInWithOAuth`. The callback route will receive a code, that needs to be exchanged for a session. Here is an example:
 
-> ⚠️ You can use the provided callback route at `/supabase/auth/callback`, the implementation of a custom callback is optional!
+> ⚠️ You can use the provided callback route at `/auth/callback`, the implementation of a custom callback is optional!
 
 ```ts [server/api/callback.ts]
 import { supabaseServerClient } from '#supabase/server'
@@ -218,7 +220,7 @@ import { supabaseServerClient } from '#supabase/server'
 export default defineEventHandler(async event => {
   const query = getQuery(event)
   const code = query.code as string
-  const next = (query.next as string) ?? '/'
+  const redirect_to = (query.redirect_to as string) ?? '/'
 
   if (!code) {
     throw createError({ statusMessage: 'No code provided' })
@@ -231,7 +233,7 @@ export default defineEventHandler(async event => {
     throw createError({ statusMessage: error.message })
   }
 
-  await sendRedirect(event, next, 302)
+  await sendRedirect(event, redirect_to, 302)
 })
 ```
 

package/dist/module.json

@@ -4,7 +4,7 @@
   "compatibility": {
     "nuxt": ">3.0.0"
   },
-  "version": "0.4.0",
+  "version": "0.4.2",
   "builder": {
     "@nuxt/module-builder": "0.8.4",
     "unbuild": "2.0.0"

package/dist/runtime/server/auth/callback.js

@@ -3,7 +3,7 @@ import { supabaseServerClient } from "#supabase/server";
 export default defineEventHandler(async (event) => {
   const query = getQuery(event);
   const code = query.code;
-  const next = query.next ?? "/";
+  const redirect_to = query.redirect_to ?? "/";
   if (!code) {
     throw createError({ statusMessage: "No code provided" });
   }
@@ -12,5 +12,5 @@ export default defineEventHandler(async (event) => {
   if (error) {
     throw createError({ statusMessage: error.message });
   }
-  await sendRedirect(event, next, 302);
+  await sendRedirect(event, redirect_to, 302);
 });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@floatingpixels/supabase-nuxt",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "description": "Supabase module for Nuxt",
   "repository": "floatingpixels/supabase-nuxt",
   "license": "MIT",
@@ -56,38 +56,46 @@
     "db:seed": "npx tsx seed.ts",
     "db:sync": "npx @snaplet/seed sync",
     "db:fullseed": "(npx @snaplet/seed sync) -and (npx tsx seed.ts)",
-    "db:dump": "pg_dump -a -h localhost -U postgres -p 54322 -f ./supabase/seed.sql --schema=public --schema=auth --inserts"
+    "db:dump": "pg_dump -a -h localhost -U postgres -p 54322 -f ./supabase/seed.sql --schema=public --schema=auth --inserts",
+    "cleanup": "pnpm nuxi cleanup && rm -rf node_modules pnpm-lock.yaml && pnpm i"
   },
   "dependencies": {
     "@supabase/ssr": "^0.5.2",
-    "@supabase/supabase-js": "^2.48.1"
+    "@supabase/supabase-js": "^2.49.1"
   },
   "devDependencies": {
-    "@nuxt/devtools": "^1.7.0",
-    "@nuxt/eslint-config": "^1.0.0",
+    "@nuxt/devtools": "^2.1.0",
+    "@nuxt/eslint-config": "^1.1.0",
     "@nuxt/kit": "^3.15.4",
     "@nuxt/module-builder": "^0.8.4",
     "@nuxt/schema": "^3.15.4",
-    "@nuxt/test-utils": "3.15.4",
+    "@nuxt/test-utils": "3.17.0",
     "@playwright/test": "^1.50.1",
     "@snaplet/copycat": "^6.0.0",
     "@snaplet/seed": "^0.98.0",
     "@types/eslint-config-prettier": "^6.11.3",
-    "@types/node": "^22.13.1",
-    "@vitest/coverage-v8": "2.1.8",
+    "@types/node": "^22.13.5",
+    "@vitest/coverage-v8": "3.0.6",
     "@vue/test-utils": "^2.4.6",
     "changelogen": "^0.5.7",
-    "eslint": "^9.19.0",
+    "eslint": "^9.21.0",
     "eslint-config-prettier": "^10.0.1",
-    "happy-dom": "^16.8.1",
+    "happy-dom": "^17.1.4",
     "nuxt": "^3.15.4",
     "playwright-core": "^1.50.1",
     "postgres": "^3.4.5",
-    "prettier": "^3.4.2",
+    "prettier": "^3.5.2",
     "release-it": "^18.1.2",
-    "supabase": "^2.9.6",
+    "supabase": "^2.12.1",
     "typescript": "5.7.3",
-    "vitest": "^2.1.9",
-    "vue-tsc": "^2.2.0"
+    "vitest": "^3.0.6",
+    "vue-tsc": "^2.2.4"
+  },
+  "pnpm": {
+    "onlyBuiltDependencies": [
+      "@snaplet/seed",
+      "esbuild",
+      "supabase"
+    ]
   }
 }