Thanks @nyannyacha 🎉

I apologize for the delay.😅 The other work is taking longer than I expected, so I decided to prioritize this.
Thanks for your patience!

No need for apologies at all!

🎉 This PR is included in version 1.59.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@elyobo is this working for you on local? I'm running v.1.65.3 but still getting:

InvalidWorkerCreation: worker boot error: Failed resolving '@...'.
    at async UserWorker.create (ext:sb_user_workers/user_workers.js:139:15)
    at async Object.handler (file:///root/index.ts:156:22)
    at async respond (ext:sb_core_main_js/js/http.js:163:14) {
  name: "InvalidWorkerCreation"
}```

@israpasos thanks for reminding me to revisit this; I had to backport some changes that I'd make locally for the specific private package code that I'd just copied in as a workaround, but after getting them sorted I have... ran into a very similar sounding issue. deno type checks and tests run as expected but the edge functions crash.

worker boot error: failed to create the graph: npm package '@my/private-package' does not exist.
    at file:///Users/elyobo/src/project/supabase/functions/_shared/auth.ts:14:8
worker boot error: failed to create the graph: npm package '@my/private-package' does not exist.
    at file:///Users/elyobo/src/uplist/supabase/functions/_shared/auth.ts:14:8
InvalidWorkerCreation: worker boot error: failed to create the graph: npm package '@my/private-package' does not exist.
    at file:///Users/elyobo/src/uplist/supabase/functions/_shared/auth.ts:14:8
    at async UserWorker.create (ext:sb_user_workers/user_workers.js:139:15)
    at async Object.handler (file:///root/index.ts:156:22)
    at async respond (ext:sb_core_main_js/js/http.js:163:14) {
  name: "InvalidWorkerCreation"

I'm running the most recent supabase

supabase --version
2.0.0

Hello @israpasos and @elyobo 😁

I think that problem is not a problem with the edge runtime itself, but a problem caused by cli.
@supabase/cli uses docker to perform deploy or serve commands, but .npmrc does not seem to be mounted.

I have confirmed that if you place .npmrc in each function folder, it is properly mounted in the docker container and the private npm registry works well.

If you have time, please open this issue with @supabase/cli.

btw, if you guys are commenting on a closed PR, I will not be able to respond quickly to your comments, so please create a new issue next time 🤗

Thanks @nyannyacha, I'll check this out this afternoon and open an issue with @supabase/cli as you suggest.

@elyobo Thank you!

@nyannyacha I've confirmed what you said above, it works if a valid .npmrc is copied to all function directories - I initially only copied it to the function that required the private package and the problem remained, it seems surprising to me (without the appropriate context) that all functions need to have the .npmrc and not just the one that actually uses the private package.

I'll open a @supabase/cli issue and reference this, thanks for your assistance.