navigator-core

Note: The options API is still evolving; expect tweaks as the project grows.

What it does

navigator-core registers two Nunjucks globals — _navigator() and _context() — for inspecting Eleventy's render context during development. Optionally, it adds a virtual debug page at /navigator-core.html that renders a full data snapshot. The globals are always available; the virtual page is off by default.

See the Navigator template in action.

_navigator() and _context() dump the full render context and may include secrets from your data layer or environment. Only use them in local development or secured environments.

Defaults

• enableNavigatorTemplate: false — globals are registered, but the virtual page is not.
• Inspector depth: 2 (how deep _inspect renders nested objects on the virtual page).

Options

Option	Type	Default	Description
enableNavigatorTemplate	boolean or [boolean, number]	false	Register the virtual page. Pass [true, depth] to set a custom inspector depth.

How it works

Example usage

{% for key, value in _navigator() %}
  <details>
    <summary><strong>{{ key }}</strong></summary>
    {% if value | isString %}
      <pre>{{ value | safe }}</pre>
    {% else %}
      <pre>{{ value | _inspect({ depth: 2 }) }}</pre>
    {% endif %}
  </details>
{% endfor %}

Tips

• Set the inspector depth with a tuple: baseline({ enableNavigatorTemplate: [true, 4] }).
• Pair _navigator() or _context() with _inspect() on any page for targeted debugging — you don't need the virtual page for that.
• The virtual page renders a large snapshot. Keep it off in production; it exposes your full data cascade.
• See Debugging & Navigator for usage patterns.

Peer deps

None.