realcoloride / node_characterai

Unofficial Character AI wrapper for node.
https://character.ai/
366 stars 81 forks source link

Puppeteer error - this library will not work in serverless architectures like Vercel #203

Open jaxomlotus opened 1 month ago

jaxomlotus commented 1 month ago

Disclaimer: I'm in no way suggesting that serverless architecture should be supported by this library - just pointing it out in case there are easy fixes to allow for it, as much of the web is moving to become serverless.

The following error is delivered when attempting to use the script hosted on a serverless platform:

_[nodecharacterai] Puppeteer - Warning: the specified Chromium path for puppeteer could not be located. If the script does not work properly, you may need to specify a path to the Chromium binary file/executable.

This version of Chromium would work on serverless, but I would not have a way to specify it in the current implementation: https://github.com/Sparticuz/chromium?tab=readme-ov-file

More details in this stackoverflow thread: https://stackoverflow.com/questions/77855572/trying-to-deploy-puppeteer-on-vercel-using-nodejs

Thanks for all your hard work on this library! The beta works great on local environments. :)

realcoloride commented 1 month ago

Hello,

I understand the issue and it is a known one that motivated the 2.x rewrite.

As the 1.x version has cloudflare protection on all endpoints, it is necessary because it uses the beta endpoints (2023).

However that branch will be deprecated soon because beta uses the new and mobile endpoints (no cloudflare). I'm not aware about the issues on Vercel but for now, I recommend you use the new beta branch for your needs, because I'm focused on the 2.x versions.

If you however really need help regarding the 1.x version for your project, let me know, but I have to remind that 1.x can break eventually when cai pulls the plug on old endpoints.

I will look into the resources you've sent when I can. Thank you for your insight.

Cheers

On Thu, Apr 17, 2025, 12:22 AM Avi Muchnick @.***> wrote:

Disclaimer: I'm in no way suggesting that serverless architecture should be supported by this library - just pointing it out in case there are easy fixes to allow for it, as much of the web is moving to become serverless.

The following error is delivered when attempting to use the script hosted on a serverless platform:

[node_characterai] Puppeteer - Warning: the specified Chromium path for puppeteer could not be located. If the script does not work properly, you may need to specify a path to the Chromium binary file/executable.

This version of Chromium would work on serverless, but I would not have a way to specify it: https://github.com/Sparticuz/chromium?tab=readme-ov-file

More details in this stackoverflow thread: https://stackoverflow.com/questions/77855572/trying-to-deploy-puppeteer-on-vercel-using-nodejs

Thanks for all your hard work on this library! The beta works great on local environments. :)

— Reply to this email directly, view it on GitHub https://github.com/realcoloride/node_characterai/issues/203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ4WO5OUATRHAZLKE75P6JL2Z3JZVAVCNFSM6AAAAAB3JNABBOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAYDAOBXGM2DONA . You are receiving this because you are subscribed to this thread.Message ID: @.**> jaxomlotus* created an issue (realcoloride/node_characterai#203) https://github.com/realcoloride/node_characterai/issues/203

Disclaimer: I'm in no way suggesting that serverless architecture should be supported by this library - just pointing it out in case there are easy fixes to allow for it, as much of the web is moving to become serverless.

The following error is delivered when attempting to use the script hosted on a serverless platform:

[node_characterai] Puppeteer - Warning: the specified Chromium path for puppeteer could not be located. If the script does not work properly, you may need to specify a path to the Chromium binary file/executable.

This version of Chromium would work on serverless, but I would not have a way to specify it: https://github.com/Sparticuz/chromium?tab=readme-ov-file

More details in this stackoverflow thread: https://stackoverflow.com/questions/77855572/trying-to-deploy-puppeteer-on-vercel-using-nodejs

Thanks for all your hard work on this library! The beta works great on local environments. :)

— Reply to this email directly, view it on GitHub https://github.com/realcoloride/node_characterai/issues/203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZ4WO5OUATRHAZLKE75P6JL2Z3JZVAVCNFSM6AAAAAB3JNABBOVHI2DSMVQWIX3LMV43ASLTON2WKOZTGAYDAOBXGM2DONA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

jaxomlotus commented 1 month ago

No problem. I should have specified that I'm using the beta 2.0 branch and these issues are impacting the new version.

realcoloride commented 1 month ago

Hello,

Are you sure? Puppeteer is not used in the new version. The puppeteer message only appears on the 1.x version.

Cheers

FarizGD commented 2 weeks ago

vercel cant load the sound library :3