:loudspeaker: Update 1 Many of you didn’t like the...
# general
f
📢 Update 1 Many of you didn’t like the naming of the
lib
directory where the stack files are kept. In v0.35.0, you can tell SST to look elsewhere by supplying the path in `sst.json`:
Copy code
{
  "name": "my-sst-app",
  "stage": "dev",
  "region": "us-east-1",
  "main": "infra/index.js"
}
A big shoutout to @geekmidas for making this happen! 📢 Update 2 @Erik Mikkelson extended the esbuild plugin support to SST code. So if you need to use
emitDecoratorMetadata
in your SST code, you can supply an esbuild config file in `sst.json`:
Copy code
{
  "name": "my-sst-app",
  "stage": "dev",
  "region": "us-east-1",
  esbuildConfig: "esbuild-config.js"
}
📢 Update 3 Added Application Load Balancer integration for
sst.Api
. You can now point an Api route to your ALB listener:
Copy code
new Api(this, "Api", {
  routes: {
    "GET  /hello": "src/lambda.main",
    "GET  /world": { albListener },
  },
});
More details on ALB integration here - https://docs.serverless-stack.com/constructs/Api#apialbrouteprops
l
@Karthik S Kumar
e
I can confirm that 0.35.0 is working great for our emitDecoratorMetadata scenario. Thanks!
In case anyone else is using it and running into problems with tests, “transpile-only” doesn’t seem to mix well with emitDecoratorMetadata. We ran into it because we were launching our mocha tests with -r ts-node/register/transpile-only, but according to https://github.com/TypeStrong/ts-node/issues/873 that can not generate the output needed
f
Thanks for confirming @Erik Mikkelson!