does SST need to be in the root directory of your ...
# general
m
does SST need to be in the root directory of your project? It seems to be creating multiple .build directories and generally having path issues for me and I suspect it’s because I have SST in a subdirectory in my monorepo
t
Yeah my new refactor fixes the multiple build dir problem but sst.json needs to be in the root and commands run from there
I can look into your general project structure and see what we can do once I'm done with that
m
I solved this for now by combining NodejsFunction with SST in a rather quick and dirty way: https://github.com/serverless-stack/serverless-stack/issues/1113#issuecomment-987814899 would love to get this cleaned up and upstream at some point. I don't need a custom SST build flow for now, NodejsFunction is sufficient
t
Nice, curious what drew you to sst if you're not using local development
m
I'd be happy to use local development (my stuff is all appsync though so not sure how helpful it would be), I'm just trying to covert a sizeable app to SST in a hurry so I'll settle for getting halfway there for now with NJSF. My project was somewhat based on a library I made, a CDK anti-framework: https://www.jetkit.dev/. Recently we started hitting the limits of that design and we're the only ones using it as far as I'm aware, so wanted to migrate to something with more of a community. Mostly what it does is keep track of function defaults and some sugar to make it really easy to create lambda functions, including figuring out exported function names and handler paths magically for you. Sadly that magic has limits, we tried wrapping things in middleware for Sentry which broke it all.
I like the stages of SST, function defaults system, env files, stack outputs, etc
I feel that's what CDK should have built in but for some reason doesn't, stuff I wanted to tackle more with jetkit/cdk but I honestly don't have time to work on it
t
Oh I've seen jetkit before!
m
oh word
there's some nifty stuff in there not sure if it would make sense in SST or not. like the metadata registry and API views
I looked at SST when I started this project but I didn't want to use Serverless so I made my own thing