Hi all, I have a question about `nextjssite` in a ...
# sst
d
Hi all, I have a question about
nextjssite
in a monorepo. My goal is to decrease the amount of time it takes to start local SST debugging. Right now, it takes between 5-10 minutes to start a debug session. The nextjs part of my monorepo project is why it takes so long to start. Does anyone know of a way I can start debugging without deploying the nextjs site? Or, perhaps, what if the nextjs construct had an option to skip invalidation, or perhaps it used regular lambda’s instead of edge lambdas to speed up the deployment? that kind of tradeoff would be fine in dev mode.
f
Hey @David Martin,
NextjsSite
should only get re-deployed if u ran
sst deploy
prior to running
sst start
.
So if you run
sst start
, kill it, and then run
sst start
again,
NextjsSite
shouldn’t get deployed and
sst start
should start up quickly.
Is that what you see?
d
Ok, testing that now
still deploys www. to be fair, there are changes that impact the www stack. since it’s in the monorepo, there’s shared code it uses….
(i pasted my stack output here but removed it since it contained keys)
to be clear, i will live with the nextjs deployment if required, but the long start times slow down dev.
f
Can you DM the redacted output to me? I will remove it after I take a quick look.
d
of course, sent
f
Just to report back here,
disablePlaceholder
was set to
true
. Removing it fixed the issue.
d
yep, the debug session just started without the nextjs deployment! thanks again @Frank