fix(types): added explicit types annotations for serverSupabaseClient and serverSupabaseServiceRole

[th1m0]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Added explicit type annotations for serverSupabaseClient and serverSupabaseServiceRole as they lose the Database type when building.

[netlify]

👷 Deploy request for n3-supabase pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	b756e00

[philliphartin]

With this addition, is there a simple way to use the Database types generated by the Supabase CLI?
https://supabase.com/docs/guides/api/rest/generating-types

[th1m0]

With this addition, is there a simple way to use the Database types generated by the Supabase CLI? supabase.com/docs/guides/api/rest/generating-types

Yes you should no longer be needed to pass in the Database types in the functions serverSupabaseClient and serverSupabaseServiceRole

This should work fine:

import { serverSupabaseClient } from '#supabase/server'

export default defineEventHandler(async (event) => {
	const client = await serverSupabaseClient(event)
})

client should have the types generated by the supabase cli automatically if you set the types path correctly in nuxt.config.ts

This was also done for the composables in #404

[larbish]

Thanks 🙏

[Zebnastien]

client should have the types generated by the supabase cli automatically if you set the types path correctly in nuxt.config.ts

@th1m0, the documentation states that the default path is "./types/database.types.ts," however, I had to specify it explicitly in nuxt.config.ts for it to work.

Thanks you both for the work <3