Question about libs and client IDs

Well the other thing you need to access the Twitch API is a logged in user to provide an access token, or using a ClientID/Secret to generate an access token.

So you need to solve that issue.

A “wrapper” doesn’t take a clientID, the user using the wrapper supplies a clientID to work with right?

So you don’t need a clientID, the user using your wrapper does.

Since this is a browser extension it runs inside the page so it can access other params that exist on the page. So naturally it’s react-ing

A library won’t use a ClientID, the user using the library supplies that

Sure for testing you’ll need to use a clientID but only you’ll be using that as users of your library will provide their own credentials. You won’t distribute the library containing your clientID.