https://serverless-stack.com/ logo
Join Slack
Powered by
I should mention there’s nothing special about the...
# seed
d
I should mention there’s nothing special about the “about” page that the error mentions. It’s seemingly random which page fails, sometimes it’s the 404 page. None of my pages have anything interesting to render, there are no SSG or ISR pages.
Is there any way I can get the .next/trace file from SEED as mentioned in this comment? https://github.com/vercel/next.js/issues/35602#issuecomment-1081827714
f
Hey @David Martin, can you try using a larger build machine? Maybe give the Large machine a try https://seed.run/docs/build-machine-types.html
If giving it more cpu/mem does not help, you can try spinning up the build container locally > clone the repo > run 
sst build
and see if it’s still slow. This is probably the quickest way to track down something specific to SEED’s build environment.
^ we can raise the timeout for your build machines if you are look to just get it to work for now
d
ok
i should have thought of using a bigger build machine…deploying now with the large one. thanks @Frank!
works like a charm!!
@Frank you are the best. thank you so much.
i give you….all the thank you GIFs https://giphy.com/explore/thank-you
f
lol HAHA.. glad it working!
^side note.. I got distracted from the VS Code high mem/cpu utilization issue.. still at the top of my todo..
will get back to it and keep you posted
d
Fyi @Frank I'm not using VS Code local debugging at all nor have I for many months. I just can't make it work. It won't stop on any breakpoints I set and then the CPU spins up as you know. Things are working with old fashioned console.log prints statements & yarn sst start for now.
Open in Slack
PreviousNext
Powered by