Block UI errors could generate 'undefined' instead of errors

Currently, missing blocks generate empty strings in codegen, leading to code that doesn't compile. Instead, they and other errors that break code generation could generate `undefined`, which would lead to runnable code. There are a few possibilities:
1. Generate the code with undefined, but still refuse to run it. I'd probably want to accompany this with different syntax highlighting for `undefined` to make it clear that it's a placeholder for an error.
2. Generate and actually run the code! Add a regexp matcher that replaces the resulting runtime errors with clearer ones and highlights or flashes the blocks that are responsible. This requires some kind of map from source locations to blocks, which could be tricky to build -- but which would also be awesome.

No se nombran archivos ni pruebas. Empieza por localizar la generación de código de bloques y el manejo de bloques faltantes; después, determina qué comportamiento ante undefined o errores de ejecución se pretende y cómo deberían identificarse los bloques responsables. Se considera terminado cuando se haya implementado el comportamiento elegido y los fallos de generación de código ya no produzcan una salida vacía engañosa.

Escrito por el modelo de indexación a partir del texto del issue.