I have two stacks and as far as I can tell the second stack should wait for the AssetsStack to deploy before it then deploys itself (I need the url for one of the routes in the api). But the value it ends up with is

https://${Token[TOKEN.186]}

which then results in the following error

error Cannot find a handler file for "https://${Token[TOKEN.186]}"

. I'm sure I've missed something obvious but I've now been starring at this problem to long to see it! lib/index.js

import MyStack from "./MyStack";
import AssetsStack from "./AssetsStack";

export default function main(app) {
  // Set default runtime for all functions
  app.setDefaultFunctionProps({
    runtime: "nodejs14.x"
  });

  const assets = new AssetsStack(app, "assets-stack");

  new MyStack(app, "my-stack", { asset_url: assets.url });

}

lib/AssetsStack.js

import  { Stack, StaticSite } from "@serverless-stack/resources";

export default class AssetsStack extends Stack {
    url
    constructor(scope, id, props) {
        super(scope, id, props);
        
        // Create a Sattic Site
        const assets = new StaticSite(this, "Assets", {
            path: 'src/build/assets/'
        })

        this.url = assets.url

        // Show the endpoint in the output
        this.addOutputs({
            "CloudFrontEndpoint": assets.url 
        });
    }    
}

lib/MyStack.js

import { Stack, Api } from "@serverless-stack/resources";

export default class MyStack extends Stack {
  constructor(scope, id, props) {
    super(scope, id, props);

    const { asset_url } = props

    // Create a HTTP API
    const api = new Api(this, "Api", {
      routes: {
        "GET /_app": asset_url,
        "$default": "src/lambda.handler",
      },
    });

    // Show the endpoint in the output
    this.addOutputs({
      "ApiEndpoint": api.url
    });
  }
}

The way cloudformation works is 100% of your code executes locally and then ships the output to AWS. This means your code has no idea what the values from AWS are when executing, which is why you're seeing a tokenized version

Yeah that's total what I'm after. A bit more background I'm playing around trying to get svelte-kit to SSR render on lambda...

It is a confusing interface haha it's referenced here: https://docs.serverless-stack.com/constructs/Api#configuring-http-proxy-routes

So /_app/ is all of the static files that SvelteKit generates when it is built for production. Everything else then runs through a node "server" which is the default route to a lambda function that maps the APIGW event to the node "server" and then spits back the html... well that's how I think it'll work!

ah gotcha that makes sense. Looks cool! If it works well we should support it directly with a SvelteSite construct

Yeah I suspect that would make a lot of people give sst a try

You'll hear me complaining about that at least once a week 😄

Oh ok so

sst start

clears the s3 bucket after a deploy 🥲

I think this is because we don't deploy the real site during sst start - in most sst start situations people are running their frontend locally. So we only really do the deployment during

sst deploy

. I did just make this ticket to disable it https://github.com/serverless-stack/serverless-stack/issues/817

That makes sense, no point uploading if you don't need to.

nice!

Hurrah so far so good, I'll have a think about what needs to change for a production environment and I can help you put a construct together for it? Thanks for all the help!

cool I'll make an issue for it and see where it lands on our roadmap