Hiya @MatHook ,
As far as I can tell, the actual cause for failure in your latest build is that it did not run at all in the latest deploy, so no files were created and the directory where you configured us to look for them was not created either and that’s what that error is reporting. You can see why here in your build logs:
If you get your build running again, then wherever it outputs files like /index.html (the root page for your site if you have one) is probably the appropriate publish directory. Looking at the last build that did run (Netlify App) it seems like client/dist is probably still correct.
As to what causes the RangeError, in the past we’ve pointed people to resources like these to debug (since it is almost certainly something about your code, likely a recursive call of some sort). Not sure they’ll help here, but the articles linked from here would be a good first-pass thing for you to start your debugging with, if you want to resume building here: