How to catch errors like - Failed to deserialize table, cannot read property records... about fontkit HOT 8 CLOSED

Noticing that when the script fails, it kills the process so all fonts after that are not being loaded. Looking at where the script fails, the font that seems to be the culprit is in the attached zip file.
Jazz.ttf.zip

from fontkit.

Here are a couple of references to the OTS parsing error:
https://bugs.chromium.org/p/chromium/issues/detail?id=527165
khaledhosny/ots#80
khaledhosny/ots@937c9c3

from fontkit.

Looking at this...
https://chromium.googlesource.com/external/github.com/khaledhosny/ots/+/refs/heads/master/docs/DesignDoc.md
I noticed that the goal of OTS was not necessarily to nuke the fonts. So I spoke too soon calling the OTS notifications 'errors'. They're actually warnings. The fonts are being loaded. Not sure if this is a problem for the app but so far it's working. I was able to overcome the font.name === undefined error as well.

from fontkit.

Those OTS issues aren't caused by fontkit. OTS is a font validator used by Chrome to prevent security issues with web fonts. If you have an issue with fontkit specifically, could you post a code example demonstrating the problem and the font in question? Thanks!

from fontkit.

Was just wondering if you had any kind of listener for those warnings and a way to suppress them.

from fontkit.

After creating a font object, is there a way to get the font file path back out of the object? Been digging around in the object and there's a lot in there. Assumed you had to have it stored in there somewhere.
Thanks.

from fontkit.

fontkit objects can be created in many ways, including from files or buffers. The filename is not held onto once the font is read into memory. You'll need to do that yourself.

from fontkit.

To prevent this, you can wrap the property call in a try-catch block

try{
   font.fullName;
 }catch(e){
   console.log(e.message);
}

from fontkit.