Support absolute path in "include"

[rockmandash]

Sometimes I need to reference files or directory outside current project, if I do this:

{
  "include": [
    "/Users/joseph/Work/company/company-components/src/Inputs/Checkbox/"
  ]
}

it outputs error:

Error filtering files: path should be a `path.relative()`d string, but got

[yamadashy]

Thanks for the suggestion @rockmandash!

You're right - using absolute paths would be a simpler way to reference files outside the current directory.
Let me look into implementing this feature.

[yamadashy]

After some consideration, I think we can handle this case better by adding rootDirs to the config.

The include option is specifically designed for pattern matching within the root directories - it defines what files to include from each root directory (like **/*.ts to match TypeScript files).

Currently, you can specify root directories through CLI:

repomix /path/to/dir1 /path/to/dir2

What if we add support for the same functionality in the config file?

{
  "rootDirs": [
    "/Users/joseph/Work/company/company-components/src/Inputs/Checkbox/",
    "./src",
    "../shared-lib"
  ],
  "include": [
    "**/*.ts",
    "**/*.js"
  ]
}

Would this approach work for you?

[rockmandash]

I understand what you’re getting at. Instead of using **dirname as the base name directly, you rely on the **dirname defined in repomix.config.json. That part makes sense.

However, I’m a bit confused about how the new rootDirs works—specifically, if I include something like "**/*.ts", wouldn’t it end up pulling in TypeScript files from all three projects when I only want those from Project 1?

One workaround might look like this:

{
  "include": [
    {
      "basePath": "/Users/joseph/Work/project1",
      "include": ["**/*.ts"]
    },
    {
      "basePath": "/Users/joseph/Work/project2",
      "include": ["**/*.js"]
    }
  ]
}

This way, I can isolate which directories and file types I’m including from each project.