Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Official Supabase Puppeteer example does not work locally #210

Open
StefanVDWeide opened this issue Dec 29, 2022 · 2 comments
Open

Official Supabase Puppeteer example does not work locally #210

StefanVDWeide opened this issue Dec 29, 2022 · 2 comments
Labels
bug Something isn't working

Comments

@StefanVDWeide
Copy link

Bug report

Describe the bug

I'm trying to follow the official puppeteer example but Puppeteer requires Deno to be run with the --unstable flag. See the documentation here:

deno run -A --unstable example.js

However, it seems that the Supabase CLI does not support passing additional parameters so running the official example locally does not work.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

  1. Init a new Supabase project
  2. Follow the steps as described here: official puppeteer example
  3. Run the example locally using the supabase functions serve command
  4. See error

Expected behavior

For the example to work locally so that it can be tested before deploying.

@StefanVDWeide StefanVDWeide added the bug Something isn't working label Dec 29, 2022
@StefanVDWeide StefanVDWeide changed the title Official Puppeteer example does not work locally Official Supabase Puppeteer example does not work locally Jan 5, 2023
@sweatybridge
Copy link

Transferring to edge runtime repo since @supabase/edge-functions is maintaining the example code.

@sweatybridge sweatybridge transferred this issue from supabase/cli Nov 9, 2023
@andreespirela
Copy link
Collaborator

Screen.Recording.2024-01-15.at.9.28.00.AM.mov

Hey there!

So I tested this and I am getting some errors very sporadicly, like it runs sucessfully and then a few requests later it fails again, it seems like it might be an issue with the connection to browserless because nothing seems pointing out to an error from the edge runtime.

Let me know if you're also running into a similar sceneario.

Attaching the video for context ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants