The plugin-tailwind template path resolves inconsistently (existence check vs file read)

[burkeshartsis]

Versions

• @terrazzo/cli: 2.0.1
• @terrazzo/plugin-css: 2.0.1
• @terrazzo/plugin-tailwind: 2.0.1

Node.js version

24.7.0

OS + version

26.0.1

Description

The @terrazzo/plugin-tailwind resolves the template path against two different bases, causing ENOENT errors when outDir in terrazzo.config.ts is anything other than ./.

In https://github.com/terrazzoapp/terrazzo/blob/main/packages/plugin-tailwind/dist/index.js, the existence check resolves relative to outDir:

cwd = new URL("./", config.outDir);                                                                                                                           
  if (!fsSync.existsSync(new URL(options.template, cwd))) // relative to outDir

But the file read uses the raw path, which resolves relative to the process cwd:

template = await fs.readFile(options.template, "utf8"); // relative to process.cwd()

When outDir differs from the process cwd (e.g. outDir: "./src/tokens/"), no single template value satisfies both checks.

Reproduction

my-project/                                                                                                                                                   
    terrazzo.config.ts
    tokens.json                                                                                                                                                 
    src/tokens/   
      tailwind-theme-template.css
                                                                                                                                                                
  // terrazzo.config.ts
  export default defineConfig({                                                                                                                                 
    outDir: "./src/tokens/",
    plugins: [
      pluginTailwind({                                                                                                                                          
        template: "./tailwind-theme-template.css",
        // ...                                                                                                                                                  
      }),         
    ],
  });

1. template: ./tailwind-theme-template.css existence check looks for ./src/tokens/tailwind-theme-template.css (found), but fs.readFile looks for ./tailwind-theme-template.css from process cwd (not found) → ENOENT
2. template: ../tailwind-theme-template.css existence check looks for ./src/tailwind-theme-template.css (not found) → "Could not locate template"

Workaround: Place the template file at both locations (or use a symlink from the project root to the file in outDir).

Expected result

The template path should be resolved consistently. Either always relative to outDir, always relative to process cwd, or always relative to the config file. The same path should be used for both the existence check and the file read.

Extra

• I’m willing to open a PR (see CONTRIBUTING.md)

[burkeshartsis]

I started looking into this and I believe I found the root cause. In plugin-tailwind/src/index.ts there are three places that resolve the template path, and they don't agree on what directory to resolve from:

• Line 49 (existence check in config hook): resolves relative to outDir
• Line 55 (file read in transform hook): resolves relative to process.cwd()
• Line 107 (header path in build hook): resolves relative to outDir

So when outDir isn't '.', the existence check passes but the file read blows up with ENOENT.

🛠️ Proposed fix

I'd like to propose that we resolve the template relative to the project root (cwd), not outDir. This feels the most natural to me and is also how the parser already resolves other user-provided paths like tokens and outDir itself. That said, plugins don't currently have access to cwd. The config() hook only receives config and { logger }. So the fix would involve two changes:

1. Add cwd to PluginHookContext in the parser and pass it through to plugin config hooks. This is additive so it won't break any existing plugins.
2. Update plugin-tailwind to use cwd from the hook context instead of deriving it from config.outDir.

This should be backwards compatible with existing configs since outDir is '.' then cwd and outDir point to the same place so nothing changes and if outDir is something else, the build would be broken today. Here's what a project config could look like after this fix. Let me know what you think.

export default defineConfig({
  tokens: ["./tokens.resolver.json"],            // resolved from project root
  outDir: "./generated/",
  plugins: [
    pluginTailwind({
      template: "./tailwind-theme-template.css", // resolved from project root
    }),
  ],
});

my-project/
├── terrazzo.config.ts
├── tokens.resolver.json              ← source file
├── tailwind-theme-template.css       ← source file
└── generated/                        ← generated output goes here