client-sdk-javascript VS plasmo

Next, we have to install the necessary packages. For TypeScript, we use @gomomento/sdk and openai.

Looking for examples? Check out this fully functional chat application built with Topics in Next.js. You can also try our work-in-progress game Acorn Hunt, built on both Momento Cache and Topics.

The introduction of the chat concept was intriguing. I had originally incorporated my ChatGPT function in a Step Function workflow, which has a relatively low maximum data size. So passing around a collection of questions and answers between states didn't seem like a great idea. With this in mind, I decided to store the conversation history in a cache using the Node.js Momento cache client.

To run the experiment, I used the Node.js Momento SDK to get and set color-hex combinations in a cache. The Momento SDK allows you to provide an auth token targeted at a specific region, so I ran a set of 1,000 API calls in the following regions.

Ooof!! It is an... interesting time right now in extensions land. The switch from MV2 to MV3 is a bit chaotic but hopefully tools like this (Bedframe) and tools like [Plasmo](https://github.com/PlasmoHQ/plasmo) start to inject some freshness in the space.

GitHub: https://github.com/PlasmoHQ/plasmo

Shameless plug, but we built the Plasmo Framework to make that (and a lot more) super easy: https://github.com/plasmohq/plasmo

Thanks! We wrote a custom Parcel runtime [1] inspired by Parcel's HMR runtime (which was too bloated and buggy for us) that injects a web socket listener into the development build of the extension.

Whenever a bundle change happens, Parcel sends it the refresh message and it either does `chrome.runtime.reload()` or `location.reload()` depending on the context.

[1]: https://github.com/PlasmoHQ/plasmo/blob/main/packages/parcel...