Should I be able to get hold of the IS_LOCAL env var inside the stack definition file? The reason I ask is that I want to extend the timeout when running locally for debug purposes.

hmm… that’s a good point. Lemme put that in.

yeah, thanks again

I've been using scope.local

Didn’t know about that

@thdxr I forgot about it. It’s not well documented either.

I guess the challenge with scope.local vs process.env.IS_LOCAL is that you only have access to scope.local within the stack, if for some reason you wanted to perform some logic based on this outside of the stack you wouldn’t have access to it. I’m struggling for a use case where that’d be the case, thought I’d mention in case others can

I pass that scope around to a bunch of helper functions

Hey guys, weirdly I couldn’t stop thinking about this lol. So after reading up on some “best practice” guidelines on environment variables, it seems we should expose a config as environment variable if its value is dependent on the environment (sst start local environment in this case).

Moved that doc around https://docs.serverless-stack.com/environment-variables