Throw on engine errors about ember-lazy-mount

[buschtoens]

Can you maybe provide more details on how to reproduce this or ideally a repo which shows the error?

[buschtoens]

I published a new release, which may fix this issue via d30931e. Can you give it a try?

[thec0keman]

Apologies for letting this go stale.

A real simple example:

{{lazy-mount 'an-engine-that-does-not-exist'}} -> silent failure
{{mount 'an-engine-that-does-not-exist'}} -> raises an exception the engine 'an-engine-that-does-not-exist' can not be found.

(Although 'does not exist' may not be accurate... but better: that isn't set up correctly yet)

[buschtoens]

This is actually intended behavior. If the engine cannot be loaded, e.g. because it does not exist, the error is yielded to the component block.

ember-lazy-mount/tests/integration/components/lazy-mount-test.js

Lines 37 to 50 in a518818

	test('it shows an error right away for a non-existing engine', async function(assert) {
	await render(hbs`
	{{#lazy-mount "not-an-engine" as |e|}}
	isLoading: {{e.isLoading}};
	error: {{e.error}};
	{{/lazy-mount}}
	`);
	assert
	.dom()
	.hasText(
	'isLoading: false; error: Error: Assertion Failed: No bundle with name "not-an-engine" exists in the asset manifest.;'
	);
	});

Can you check, whether this works as expected?

#93 is about making this info available as a hook as well, so you can trigger something in response to a failure.

[thec0keman]

Oh interesting, I didn't know about this! Okay, I think this should be closed then.

Thanks!