Allow missing breadcrumb navigation items

[lhokktyn]

When the eleventyExcludeFromCollections option is enabled, the collections.all array will not contain all pages, resulting in eleventyNavigationBreadcrumb() throwing a "Node does not exist" exception, which manifests as an opaque nunjucks error that is difficult for the reader to trace.

This change uses the allowMissing option of eleventyNavigationBreadcrumb() to effectively allow this scenario to fail silently (no breadcrumb will appear at all rather than failing to compile).

In our case, we use eleventyExcludeFromCollections to exclude some dynamically generated pages from collections.all for performance reasons.

We're using 11ty v3.0.0, but allowMissing is a valid option for eleventyNavigation@0.3.5.

@paulrobertlloyd I figured this would be a relatively safe option to hardcode into the base template, but do you think it warrants exposing as an option to consumers of this plugin?

[paulrobertlloyd]

@lhokktyn Thanks for this. This would certainly prevent the annoying and opaque errors that are too often a side-effect of eleventyNavigation.

I’d be tempted to add to base template as you have here, and make it an option later should that be needed.

Will take a closer look some time later this week, along with the order of searchPaths, and hopefully put together a minor release with these 2 changes.