As promised...
The Discord link on the node page's footer was fixed and I got through to the dev team (thanks Shaquu!).
The dev team suspected a node type conflict existed and was causing this fatal error. The solution was a node-red restart which worked to solve this issue.
I am new to using node-red, so I am not sure if these types of "collisions" are common. If they were, then we would certainly want some alerting or automated resolution for this type of problem.
For now, resolution will start with a restart!
