Jack Steam

@Toumash thank you! @heymaaz Contributions are welcome! There's a link at the bottom of the doc to the Google Dev Docs for Chrome Extension service workers.

There's no minimal reproduction, so I can't be sure, but my guess is that this is due to [custom elements not being implemented in content scripts](https://stackoverflow.com/questions/30022350/registering-a-custom-element-from-a-chrome-extension). The Vite error overlay...

This issue might be fixed in `@crxjs/vite-plugin@^2`, which in beta right now; you can test it using: ```sh npm i @crxjs/vite-plugin@beta -D ```

Vite uses WebComponents for the error overlay, but content scripts don't support WebComponents out of the box. CRXJS adds the polyfill in development but not in production. If you can...

Thanks for the heads up! IIRC, this is a limitation of Chrome. See https://github.com/crxjs/chrome-extension-tools/discussions/280#discussioncomment-2562533 The error message is different than in the past. I'll set aside some time to investigate...

This would be easy to do, I'd look here: https://github.com/crxjs/chrome-extension-tools/blob/534a5b64a4543281ac062e6fbe6761eb54491ca2/packages/vite-plugin/src/node/plugin-manifest.ts#L395 PR's are welcome 😺

Just to add a little more context: The async functions `aget_embedding` and `aget_embeddings` raise a TypeError, implying that `client.embeddings.create` is not an awaitable function. https://github.com/openai/openai-cookbook/blob/c1bd61f944d46e3539b4a136e4273df79b1b7eed/examples/utils/embeddings_utils.py#L27-L35 https://github.com/openai/openai-cookbook/blob/c1bd61f944d46e3539b4a136e4273df79b1b7eed/examples/utils/embeddings_utils.py#L50-L61 After copying the preceding...

I'd love to see Anthropic support now that Claude 3.5 Sonnet has surpassed OpenAI.

This seems like a bug to me! We're also encountering it.

@Bhuvana-Priya This is brilliant! Kudos to the MS Edge development team!