You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a couple of confusing hours trying out open-next with SST, I noticed that SST does not use open-next at all, the page linked in the readme points to https://docs.sst.dev/constructs/NextjsSite where you see they depend on serverless-next.js dependency @sls-next/lambda-at-edge.
Looking at the Builder class used it does not use anything from open-next, you are basically deploying a serverless-next.js wrapper using SST.
Can the reference to SST be removed from the Readme? It now indicates that you can use SST for deployment but in fact it has nothing to do with open-next.
Regards,
The text was updated successfully, but these errors were encountered:
Hi,
After a couple of confusing hours trying out open-next with SST, I noticed that SST does not use open-next at all, the page linked in the readme points to https://docs.sst.dev/constructs/NextjsSite where you see they depend on
serverless-next.js
dependency @sls-next/lambda-at-edge.Looking at the
Builder
class used it does not use anything from open-next, you are basically deploying aserverless-next.js
wrapper using SST.Can the reference to SST be removed from the Readme? It now indicates that you can use SST for deployment but in fact it has nothing to do with open-next.
Regards,
The text was updated successfully, but these errors were encountered: