Shaun
Shaun
this might cause the issue that updating lambda aliases breaks website for a short duration. I see it happen very often
can anyone merge the PR?
why is this expected? so pool is not suppose to use proxy?
thanks! any example of using proxy directly?
I confirm this is a bug. when Pool is used, it's not picking up `{ ..., dispatcher: new ProxyAgent("...")}`, nor `setGlobalDispatcher(proxyAgent)`
anyone can take care of this?
I found some tests are failing. After you agree on my approach, I will add tests and modify readme.
> Update: `SST` v2 `NextjsSite` construct has integrated w/ `open-next`. There's still a few things to iron out like `middleware` redirection and `viewer request vs origin request` policy. > >...
> so you mean still use `npx create-sst@latest my-project' to create a ss1 project. but import { NextjsSuite } from https://github.com/serverless-stack/sst/tree/sst2/packages/sst/src/constructs right?
> 1. create a new Next.js app npx create-next-app@latest > 2. go into the Next.js app and install npm install --save-dev sst@rc > 3. add an sst.config.js > > ```ts...