Bug report
Describe the bug
There seem to be some imports for npm that cause edge functions to fail when deployed even though they work fine locally.
The error spit back from logs is: worker boot error: failed to read path: No such file or directory (os error 2).
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
- Simply run 'supabase functions new hello-world'
- Jump into index.ts and add: 'import { Helius } from "npm:helius-sdk";' to the top.
- Run supabase serve to see that it's all working locally.
- Run supabase deploy and hit the endpoint to get the aforementioned error.
Expected behavior
I would expect serve and deploy to both work fine or both fail.
I'm noticing this issue across multiple different npm package imports.
System information
- OS: macOS
- Browser: chrome
- Version of supabase-cl: 1.165.0
Additional context
index.ts
import { Helius } from "npm:helius-sdk";
export const helius: Helius = new Helius("");
Deno.serve(async () => {
const data = {
message: `Helius: ${helius}`,
};
return new Response(JSON.stringify(data), {
headers: { "Content-Type": "application/json" },
});
});
Bug report
Describe the bug
There seem to be some imports for npm that cause edge functions to fail when deployed even though they work fine locally.
The error spit back from logs is: worker boot error: failed to read path: No such file or directory (os error 2).
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
I would expect serve and deploy to both work fine or both fail.
I'm noticing this issue across multiple different npm package imports.
System information
Additional context
index.ts