Unable to set absolute path for includes

[ggodlewski]

Version

1.12.1

Platform

Linux

What steps will reproduce the bug?

I want to keep includes outside of content directory using absolute path. My config is following:

import * as path from "https://deno.land/std@0.57.0/path/mod.ts";
import lume from "lume/mod.ts";
import prism from "lume/plugins/prism.ts";
import postcss from "lume/plugins/postcss.ts";
import metas from "lume/plugins/metas.ts";

const __dirname = path.dirname(path.fromFileUrl(import.meta.url));

const site = lume({
    includes: path.join(__dirname, "theme"),
    src: "./content",
    dest: "./build",
});

site.use(prism());
site.use(postcss());
site.use(metas());

export default site;

I'm getting error:

Caused by Error: Couldn't load this file
- fullPath: /home/gg/workspaces/lumetest/content/home/gg/workspaces/lumetest/theme/layout.njk

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior?

Do not concatenate includes path with content path if it starts with /

What do you see instead?

I want to be able to set any path in my filesystem for the includes/theme

Additional information

No response

[oscarotero]

This is not a bug but the expected behavior. Everything in Lume must reside in the src folder. If you want to load files from different places, you can configure remote files. For example:

site.remoteFile("_includes/layout.njk", import.meta.resolve("./theme/layout.njk"));

More info here: https://lume.land/docs/core/remote-files/

[shuaixr]

@oscarotero I really hope lume can have more freedom in path configuration. I can't use a structure like this in lume:

├── _config.ts
├── deno.json
└── src
    ├── layouts
    │   ├── base.njk
    │   └── index.njk
    └── pages
        └── index.md

[oscarotero]

@shuaixr What's the problem with this structure? You can configure Lume to use the src folder.