Bot releases are hidden (Show)
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
A couple of optimizations made to the StaticSite
:
sst deploy
and the site hasnβt changed, SST will skip uploading the files to S3 and invalidating CloudFront cache. This will save you a couple of minutes per deploy when you are just working on your backend.sst start
, SST will deploy a placeholder site, and will not re-deploy on changes. This is to ensure sst start
always start up quickly. And itβs assumed that you have your website running locally when you are working on it.Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
We made a minor change to how StaticSite
handle 404 pages for SPAs (ie. React, Vue, Angular). If you are using StaticSite
to deploy SPAs, make sure to configure errorPage
like this:
import { StaticSite, StaticSiteErrorOptions } from "@serverless-stack/resources";
new StaticSite(this, "ReactSite", {
path: "path/to/src",
+ errorPage: StaticSiteErrorOptions.REDIRECT_TO_INDEX_PAGE,
buildCommand: "npm run build",
buildOutput: "build",
});
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Revert #476 App: add account property (@fwang)
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
AppSyncApi: if you are using the AppSyncApi
construct, existing resolvers need to be removed, and then added back. To add a bit of background, Resolvers were previously created within a DataSource's construct scope. When you try to update the DataSource for the resolver, deployment will fail with the CloudFormation error Only one resolver is allowed per field
. By creating the Resolvers within the AppSyncApi's construct scope, this error will not happen. But to make this change, existing resolvers need to be removed; and then add them back in the next deployment. Read more about the issue here - https://github.com/serverless-stack/serverless-stack/issues/417
--increase-timeout
flag to allow testing with breakpoints (@fwang)Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
#410 sst diff: compare and diff local CF templates against the deployed stacks (@fwang)
You can run sst diff
to compare the current version of stacks in your app with the already-deployed version.
# Diff all stacks
npx sst diff
# Diff a specific stack
npx sst diff api-stack
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]
Published by fwang over 3 years ago
Update using:
$ npm install --save --save-exact @serverless-stack/[email protected] @serverless-stack/[email protected]