https://serverless-stack.com/ logo
Join Slack
Powered by
Would live lambda development work if I deploy a s...
# sst
a
Would live lambda development work if I deploy a stage via seed and then start it locally via 
npx sst start
. When I attempt this, my requests work but they don’t get logged in the console and my changes also don’t get reflected.
f
Hey @Ashishkumar Pandey, it should work, b/c deploying through SEED has no difference as running 
npx sst deploy
locally.
Just to clarify, when you run 
sst start
, u don’t see the requests in the console?
a
Yeah I have the same problem 😞
I have to remove all the stacks and start again to make it work.
Not even with seed, just doing locally.
f
Something is definitely wrong here.. @Adrián Mouly how often does that happen? everytime when you do 
sst start
after an 
sst deploy
?
a
Actually I do start first… make some changes, then I do deploy.
And then maybe the other day I want to do start again, but the requests never gets in.
After removing everything, then doing start again, works.
Going to try again in a couple of hours, if it doesn’t work going to ping you and maybe we can do screenshare.
f
That’d be real helpful @Adrián Mouly
Oh I think I figured out @Ashishkumar Pandey’s issue… can you remove 
.build
folder in your SST app locally, and try running 
sst start
again?
@Adrián Mouly maybe give that a try too if you run into this again.
a
Ok going to try it.
a
I don’t remove everything, I remove the stack which contains that API and then run sst start again, This makes it work. @Frank, okay, I’ll replicate the issue and try your solution and let you know.
a
Yeah I remove all, just because there is a command.
But it’s the same.
a
you can remove a single stack using 
npx sst remove <stage>-<app-name>-<stack-name>
a
Yeah.
f
or just 
npx sst remove <stack-name>
a
I was just lazy to do that.
And used remove..
But the result is the same, the stack that I was testing got deleted, and then created again, and worked.
a
I have some custom domains and certificates, which take a lot of time to deploy if removed completely so I try and avoid removing everything.
a
Yeah that makes sense for sure.
Anyway, removing is not ideal.
a
@Frank your solution worked, thanks, this needs to be documented though. I could add this as a gotcha in the working locally section of the docs unless you’ve a fix in mind.
f
Yeah.. I put in an optimization for making 
sst start
start up quicker, and this is a bug. I’m going to put in a fix this week - https://github.com/serverless-stack/serverless-stack/issues/459
a
okay, sounds good. Thank you. 🙏
Open in Slack
PreviousNext
Powered by