[oleeskild]

Problem

Fixes #786 — navigation order is silently ignored for any note affected by a path rewrite rule, even after re-checking and re-saving the order in the plugin.

Root cause

When a path rewrite rule applies, the plugin writes a dg-path into the published frontmatter that includes the .md extension (e.g. Path Rewriting/note.md → dg-path: note.md).

getPermalinkMeta in filetreeUtils.js built the file-tree leaf key with folders[last] += ".md", assuming dg-path had no extension (true for manually-set dg-path and for filePathStem, which Eleventy strips). For rewrite-rule notes this produced a double extension: note.md.md.

The stored navigationOrder uses stems (note), and sortTree's resolver only tries note / note.md. The note.md.md key never matched, so the note dropped to default sort and the custom order was lost. This is why the bug only appears with rewrite rules.

Fix

Strip a trailing .md before re-appending it, so leaf keys are always single-extension regardless of whether dg-path carried the extension. Only .md is stripped (not arbitrary dots), so names like my-note-v1.2 are preserved.

Also in this change:

• Declared the implicit globals in assignNested (previously only worked in CommonJS sloppy mode; threw under strict/ESM and leaked globals).
• Converted filetreeUtils.test.js to ESM imports so it actually runs under vitest run (it was using jest-style globals and not running in the suite).

Tests

Added 3 tests covering the rewrite-rule scenario (root, nested folder, and dot-in-name). Confirmed they fail before the fix (note.md.md keys) and pass after.

Test Files  6 passed (6)
     Tests  223 passed (223)

🤖 Generated with Claude Code