Andreas Thomas

Thanks, that must have slipped through I'm on vacation starting tomorrow, so unfortunately this has to wait until ~22nd-25th of august. But I'll add it right after

hmm, looks like it's already implemented, what made you think it's not available?  @magicspon

Hey @donaldrevel , I've created a release candidate with this feature `npm install @upstash/[email protected]` You can now create a new script instance and then execute it. ```ts import { Redis...

It's in `v1.12.0` Let me know once you have time to check and have some feedback :)

Will do this together with aws lambda next week

Hey @cathykc, thank you for reporting this. We recently found something similar in nextjs I believe. For some reason it didn't load environment variables properly, when creating such a utility...

I will take a look at this on monday or tuesday. It should be fairly easy to reproduce, thanks to your code snippet and explanation above.

Hey @cathykc, I created [an example](https://github.com/upstash/upstash-redis/tree/main/examples/nextjs_export) but it works as expected. I also tried using default exports, that sitll works. Can you compare it with your code and let me...

Hmmm, it might be caused by `getServerSideProps`. I'll play around with it, thanks for sharing.

Hey @Ali-Hussein-dev @cathykc I tried this again and it worked just fine. ``` git clone https://github.com/Ali-Hussein-dev/bug-reproduce.git cd bug-reproduce yarn add @upstash/redis@latest UPSTASH_REDIS_REST_URL=... UPSTASH_REDIS_REST_TOKEN=.. yarn dev ``` Also tried it deployed...