Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion internal/functions/new/templates/deno.json
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
{
"imports": {}
"imports": {
"@supabase/functions-js": "jsr:@supabase/functions-js@^2"
}
}
2 changes: 1 addition & 1 deletion internal/functions/new/templates/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
// This enables autocomplete, go to definition, etc.

// Setup type definitions for built-in Supabase Runtime APIs
import "jsr:@supabase/functions-js/edge-runtime.d.ts"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nyannyacha is this a problem we need to address?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The mentioned lints appear to have been introduced in Deno v2.5.
Since we're currently fixed at Deno 2.1.4, not fixing the lints wouldn't cause much impact. However, the problem is that we can't prevent users from using the latest version of Deno.

So in my opinion... yes, I agree to change the template style so the lints don't complain.

import "@supabase/functions-js/edge-runtime.d.ts"

console.log("Hello from Functions!")

Expand Down
Loading