While experimenting with block customization, with Chrome as my browser, I ended up with an error . . .
Uncaught TypeError: Invalid block definition for type: UV99_999
at new Block$$module$build$src$core$block (blockly_compressed.js:994:486)
at new BlockSvg$$module$build$src$core$block_svg (blockly_compressed.js:1242:349)
at WorkspaceSvg$$module$build$src$core$workspace_svg.newBlock (blockly_compressed.js:1670:444)
at appendPrivate$$module$build$src$core$serialization$blocks (blockly_compressed.js:193:210)
at appendInternal$$module$build$src$core$serialization$blocks (blockly_compressed.js:190:436)
at append$$module$build$src$core$serialization$blocks (blockly_compressed.js:189:89)
at BlockSerializer$$module$build$src$core$serialization$blocks.load (blockly_compressed.js:624:1028)
at Object.load$$module$build$src$core$serialization$workspaces [as load] (blockly_compressed.js:419:209)
at load (serialization.js:30:1)
at eval (index.js:38:1)
. . . that won't go away, even though I have removed the offending block type, killed the server, rebooted, and even reinstalled the entire sample-app package. I suspect the serialized data, wherever it is, needs to be flushed, but I don't know how to get to it. On the other hand, when I open localhost in Edge, no problem, everything is running as expected.
Would anyone have a suggestion for how I can break out of this doom loop in Chrome?
Thanks very much!
--Steve