Been moving the furniture around with my SLS/SST h...
# sst
o
Been moving the furniture around with my SLS/SST hybrid app. Now when I run
sst start
I get my compiled code turning up outside of the
.build
folder. That’s where its supposed to go, right?
t
compiled code right now goes to
${srcPath}/.build
for functions
And for everything else it goes alongside
sst.json
o
The .js and .js.map files don’t count as compiled code? I think it used to go in .build - at least wherever it was getting compiled was getting .gitignored
I used to have my sst.json at the top level, but I need two SST stacks, so ended up moving it inside
services/sst
(and another one exists at
resources/sst
- need one stack deployed before all the SLS stuff in seed, and another after the SLS stuff(
t
Yeah that seems weird I'm not sure why code is ending up in there. Looks like a bug
I should be able to reproduce this with 2 sst projects right
Can you actually send me a minimum description of the file hierarchy, bit hard to tell from the image
o
yeah will DM
In case anyone is following along, Dax said this looks like a bug in SST, but its hard to fix because they really need to consolidate and rationalise all the file path code that’s spread around SST
I ended up putting my services as a sub-directory of where sst.json lives, instead of as a sibling. Basically following the approach in the typescript-starter, but multiple times in the same monorepo