How often does it reproduce? Is there a required condition?
Every time, no additional requirements or conditions.
What is the expected behavior?
You'd expect that a ./ url would be relative to the encapsulating file, which is how import works, thus you'd expect the resulting URL from the example to resolve to /example/thing.html, which also mirrors NextJS' dynamic routes:
What do you see instead?
Lume instead treats the multi-page generator as a folder; the resulting URL from the example is actually /example/[test]/thing.html, or, if you disable prettyUrls, /example/[test].html/thing.html. This means that ./ has a radically different meaning in different circumstances within the same file, such as:
Version
1.13.1
Platform
Linux
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Every time, no additional requirements or conditions.
What is the expected behavior?
You'd expect that a
./
url would be relative to the encapsulating file, which is howimport
works, thus you'd expect the resulting URL from the example to resolve to/example/thing.html
, which also mirrors NextJS' dynamic routes:What do you see instead?
Lume instead treats the multi-page generator as a folder; the resulting URL from the example is actually
/example/[test]/thing.html
, or, if you disable prettyUrls,/example/[test].html/thing.html
. This means that./
has a radically different meaning in different circumstances within the same file, such as:Additional information
No response