Releases: anomalyco/sst
v0.63.0
Major changes to NextjsSite
The NextjsSite construct uses the @sls-next/lambda-at-edge package from the serverless-next.js project to build and package your Next.js app to a structure that can be deployed to Lambda@Edge and CloudFront.
Prior to this release, SST used to include the @sls-next/lambda-at-edge package as a dependency. It caused two problems:
- You cannot use a different version of
@sls-next/lambda-at-edge @sls-next/lambda-at-edgeis installed even if you are not using theNextjsSiteconstruct
Starting with this release, you are responsible for installing @sls-next/lambda-at-edge as a dependency in your SST app to use the NextjsSite construct.
What do I need to do
npm install -s @sls-next/lambda-at-edge
// or
yarn add @sls-next/lambda-at-edgeThat's it! This should be a seamless transition for most people without any code changes. However, if you are hardcoding the bucket name, you need to change the name because this release will replace the bucket, and CloudFormation cannot replace it with the same name. For example, change this:
new NextjsSite(this, "Site", {
path: "path/to/src",
s3Bucket: {
bucketName: "my-bucket",
},
});to
new NextjsSite(this, "Site", {
path: "path/to/src",
s3Bucket: {
bucketName: "my-new-bucket",
},
});Update using:
$ npx sst update 0.63.0
$ yarn sst update 0.63.0v0.62.0
v0.61.3
Major changes to StaticSite
We made some changes to the StaticSite, ReactStaticSite, and ViteStaticSite constructs to speed up the deployment time.
Prior to this release, on each deployment, the site is deployed to a new folder inside the S3 bucket, and the CloudFront distribution is updated to point to the new folder. This process can sometimes take more than 5 mins. On rare occasions, this process can also causes intermittent downtime for low traffic sites. Starting with this release, the site is deployed to the root of the S3 bucket. And each subsequent deployment overwrites the files of the previous deployment.
Who is affected
This should be a seamless transition for most people without any code changes. However, if you are hardcoding the bucket name, you need to change the name because this release will replace the bucket, and CloudFormation cannot replace it with the same name. For example, change this:
new StaticSite(this, "Site", {
path: "path/to/src",
s3Bucket: {
bucketName: "my-bucket",
},
});to
new StaticSite(this, "Site", {
path: "path/to/src",
s3Bucket: {
bucketName: "my-new-bucket",
},
});This affects the StaticSite, ReactStaticSite, and ViteStaticSite constructs.
🚀 Enhancement
- #1350 StaticSite: speed up deployment (@fwang)
- #1342 Auth Console (@thdxr)
- #1348 Auth: add custom email and sms sender triggers (@fwang)
Update using:
$ npx sst update 0.61.3
$ yarn sst update 0.61.3v0.61.2
v0.61.1
🚀 Enhancement
🐛 Bug Fix
- #1336 Generate truly unique function local ids (@thdxr)
- #1340 Do not ignore entire stacks folder for function watcher (@thdxr)
- #1303 Add support for AWS GovCloud (@mendellerner)
Committers:
- Mendel Lerner (@mendellerner)
Update using:
$ npx sst update 0.61.1
$ yarn sst update 0.61.1v0.61.0
📣 New Console Command
This release has a new sst console command that can point the console at different environments outside of your local (sst start). This allows you to look at CloudWatch logs and manage your app in production.
Learn more about it here: https://docs.serverless-stack.com/packages/cli#console
npx sst console --stage=production🚀 Enhancement
- #1322 Add console command + cloudwatch logs (@thdxr)
- #1326 Function: show helpful error message when esbuild plugin is not found (@fwang)
- #1324 Support GraphQL formatPayload callback (@thdxr)
Update using:
$ npx sst update 0.61.0
$ yarn sst update 0.61.0v0.60.11
v0.60.9
v0.60.8
🚀 Enhancement
-
#1311 Cli: hide exports from outputs created by CDK (@fwang)
If this error seems familiar to you, we added automatic early detection for this issue.
❌ dev-stackA failed: Export dev-stackA:ExportsOutputRefTableArn30B25837ED330C0 cannot be deleted as it is in use by dev-stackBSST will temporarily add the exports that are still in use. Read more about how it works.
-
#1310 Cli: detect exports still in use and temporarily add to template (@fwang)
🐛 Bug Fix
📝 Documentation
Update using:
$ npx sst update 0.60.8
$ yarn sst update 0.60.8v0.60.6
🚀 Enhancement
🐛 Bug Fix
- #1308 Cli: fix stack changes not redeployed in sst start (@fwang)
- #1302 NextjsSite: fix placeholder lambda functions (@fwang)
- #1301 Cli: disable xray tracing for local invocation (@fwang)
- #1298 Set aws-cdk-lib as external when transpiling CDK code (@fwang)
📝 Documentation
Update using:
$ npx sst update 0.60.6
$ yarn sst update 0.60.6