"Node globals cannot be used in browser" about openai-streams

[Johnrobmiller]

I possibly found the problem

./node_modules/nextjs-openai/node_modules/openai-streams/dist/globs/node.js

This is in the nextjs-openai module, not this one. However, there openai-streams is installed within the nextjs-openai module, and because I'm using nextjs-openai on the client, this might be the reason it's throwing this error

[ctjlewis]

Ah, yes. I stupidly re-exported the server-side only library at the client-side entry-point. Very true John, that is absolutely the problem, my bad. Let me try to fix it.

Thanks for being patient through these issues.

[ctjlewis]

Hey, are you trying to use await OpenAI() on the client?

This would leak your API key into the client bundle, this is an older version of the library freaking out and disallowing it.

If you're just using it in getServerSideProps() or something, upgrading should get rid of this but if it didn't you could await import("...") inside getServerSideProps() to make sure it doesn't end up in the client.

[Johnrobmiller]

It's only being imported in one place, and that's in the triniti api route. Also, I double checked to make sure that route isn't being accidently called on a client page. We are using middleware, but I would hope that the middleware isn't getting exposed to the client, would be bad news for security
Also, I'm on latest (1.0.19)

SS:

[ctjlewis]

So sorry for that again @Johnrobmiller. This should be fixed on latest. Docs should be up to date as well.

yarn add nextjs-openai openai-streams

# -or-

npm i --save nextjs-openai openai-streams