kyt | Starting a new JS app? Build, test and run advanced apps with kyt 🔥 | Frontend Framework library

I'm working on a project where I have a file that the program accesses to get information on different crimes from a range of years. It then needs to add up the crime based on the type and put it into a file. I have the first part down, it does access the file and adds up the crime amounts by type but when I open the file that is created, it's not printing out correctly and I can't seem to find what's wrong.

This is what prints out on the file:

¬í sr java.util.HashMapÚÁÃ`Ñ F loadFactorI thresholdxp?@ w
t Violent Crimes Totalsr java.lang.Integerâ ¤÷‡8 I valuexr java.lang.Number†¬•”à‹ xp ¤Mt Rapesq ~ jt Vehicle Theftsq ~ {™t Aggravated Assaultsq ~ kƒt Homicidesq ~ t Robberysq ~ N t NonResidential Burglarysq ~ kÿt Residential Burglarysq ~ ã~t Property Crimes Totalsq ~ ïit Theftsq ~ :cx

With the system.out.println it prints:

{Violent Crimes Total=42061, Rape=1898, Vehicle Theft=97177, Aggravated Assault=27523, Homicide=399, Robbery=19981, NonResidential Burglary=27647, Residential Burglary=58238, Property Crimes Total=454505, Theft=342627}

The system print out is what I'd like to show up in the file.

I have a React application that renders on both client and server. When any component's render() fails (due to a bug in my code, e.g. trying to read a property of an undefined object), then if I'm navigating from another page in the browser, then I get a full stack trace in the browser developer console.

However, when I trigger a server-side render of the same code (by directly pointing the browser to the problematic route that contains the faulty component), then I just get errors like these in the server's console:

(node:97192) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'tagDefinitionId' of undefined

With no stack trace, it's a little hard to debug.

QUESTION: Is there a way to blanket-catch-all render() failures during server-side renders?

The code that triggers a server-side render in response to a Node-Express endpoint being requested is below. I believe the unhandled promise rejection occurs inside renderToString(), but this function returns a string, not a promise.

`