Well, this behavior is similar to previous behavior... Which does not answer the question ...

This error is triggered in `designerFrame` [there](https://github.com/enyojs/ares-project/blob/ENYO-3632/deimos/source/designer/designerFrame/designerFrame.js#L461):
```
var kindConstructor = enyo.constructorForKind(inKind.name);

if (!kindConstructor) {
	errMsg = "No constructor exists for ";
	enyo.warn(errMsg, inKind.name);
	this.sendMessage({op: "error", val: {triggeredByOp: cmd, msg: errMsg + inKind.name}});
	return;
} else if(!kindConstructor.prototype) {
	errMsg = "No prototype exists for ";
	enyo.warn(errMsg, inKind.name);
	this.sendMessage({op: "error", val: {triggeredByOp: cmd, msg: errMsg + inKind.name}});
	return;
}
```

When this happens, the state of `designerFrame` is not altered and is consistent with a `ready` state. This is fine but still does not answer the question above.

The real question is: how this errors are supposed to happen ? Depending on the cause, it may be better to send the user back to editor mode. 

Do you have an idea ?