6
Edge Functions: Allow package.json without import_map.json
Source: supabase/supabase#23239 · opened by @jacob-israel-turner
Hi friends! I'm just getting started using Supabase edge functions. Most of my codebase is written for either a Node.js or browser environment, and I heavily utilize pnpm and package.json/pnpm for module resolution. I'm using an NX monorepo, so dependencies are pinned for all libraries and applications. I was hoping to utilize Deno's [package.json]( compatibility out-of-the-box. In my editor, it seems to sync up to the correct version in my package.json automatically. However, once I run supabase functions serve, I get this error: I assume this is because edge functions use their own runtime. Unfortunately I don't have much insight into the problem or solution, since this is my first time using Deno. Fortunately, if I add this import map the problem goes away: One minor concern is that I'll need to do this for every node module that this function will rely on, which I expect to be significant. But, not a huge deal, I'll just have to f…
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable Syncing of Vault and Edge Function Secrets
1 vote · 0 comments
NestJS Support in Supabase Edge Functions
17 votes · 0 comments
Improving the functionality of Edge Functions
3 votes · 0 comments
Feature Request: Add Descriptions for Edge Functions
2 votes · 0 comments
Can we get an example where functions and types are shared between front-end code and edge functions?
12 votes · 0 comments
No comments yet.