NextJS + web support

[avaer]

I understand that this library uses child_process to shell out to some functionality, but this library also duals as a client wrapper for the API, so it seems reasonable to want to include it in the frontend (which might not need any of the child_process functionality, it just wants to access the API from TS).

---

I see there have been other issues related to child_process, I am getting similar:

./node_modules/.pnpm/@elevenlabs+elevenlabs-js@2.20.0/node_modules/@elevenlabs/elevenlabs-js/wrapper/play.js
Module not found: Can't resolve 'child_process'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/.pnpm/@elevenlabs+elevenlabs-js@2.20.0/node_modules/@elevenlabs/elevenlabs-js/wrapper/index.js
./node_modules/.pnpm/@elevenlabs+elevenlabs-js@2.20.0/node_modules/@elevenlabs/elevenlabs-js/index.js

---

Is there any plan to (once again) support web environments with this library? ^2.3.0 worked previously on the web.

[avaer]

I am aware of @elevenlabs/client and @elevenlabs/react but these libraries are different -- they are for the agents SDK, and do not seem to provide API wrapping functionality like this library does.

[avaer]

For anyone interested, stubbing could maybe be used to support web: #294

[PaulAsjes]

What's your use case for using this library on the frontend? We don't recommend it as it would mean exposing your API key to the client.

This library is designed to operate in server environments, and there are no plans to make it work on the client long term.
As such I would advise not using it to perform any client side operations

[codeit-ninja]

What's your use case for using this library on the frontend? We don't recommend it as it would mean exposing your API key to the client.

This library is designed to operate in server environments, and there are no plans to make it work on the client long term. As such I would advise not using it to perform any client side operations

I have a use case for this, tauri. This would open us to make use of the SDK in Tauri apps.

[avaer]

What's your use case for using this library on the frontend? We don't recommend it as it would mean exposing your API key to the client.

1. Open source electron app that has no server
2. Serverless agents that don't run on node
3. Web-only development environments
4. Bouncing the calls off of a proxy

Many others have similar use cases, we've just been using old versions of the lib or hacks.

I did solve my problem by fixing the library's node deps, but I don't really see why it couldn't be officially supported. Considering that it did work before.

[kraenhansen]

Thanks for raising this, @avaer. You make a great point about supporting runtimes beyond Node.js. I'm labeling this as tracking to gauge broader interest.