I think this is a reasonable change. I'll need to think through any potential b/c issues in case this needs to be released as v0.6.0. We also might want to do this for implicit config lookup and not just when using tailwindConfig in the prettier config. We also will maybe want to fallback to base dir if filepath is undefined (can happen in programmatic uses of Prettier).

I'll take a look at this some time this afternoon!

Thanks! I've added the fallback as well. We already use this patch on top of v0.4.1

We are also having a similar issue which would be fixed by this change. Additionally I would like to propose a similar config option to what the Tailwind vscode intellisense extension has, which is a mapping of glob patterns to tailwind config files like this:

"configPath": {
  "./packages/A/tailwind.config.ts": "packages/A/**"
  "./packages/shared/tailwind.config.ts": ["packages/B/**", "packages/C/**"]
}

@flowreaction Prettier itself supports this with configuration overrides. No additional config options needed.

You should be able to use a config that looks something like this:

{
  // …
  "overrides": [
    {
      "files": "packages/A/**",
      "options": {
        "tailwindConfig": "./packages/A/tailwind.config.ts"
      }
    },
    {
      "files": ["packages/B/**", "packages/C/**"],
      "options": {
        "tailwindConfig": "./packages/shared/tailwind.config.ts"
      }
    }
  ]
}

@mircoba I haven't forgotten about this change btw. Just been super busy. I plan to look at this again soon (though it might wait until after React conf)

@flowreaction Prettier itself supports this with configuration overrides. No additional config options needed.

You should be able to use a config that looks something like this:

{
  // …
  "overrides": [
    {
      "files": "packages/A/**",
      "options": {
        "tailwindConfig": "./packages/A/tailwind.config.ts"
      }
    },
    {
      "files": ["packages/B/**", "packages/C/**"],
      "options": {
        "tailwindConfig": "./packages/shared/tailwind.config.ts"
      }
    }
  ]
}

Awesome, thanks for sharing this! 🙏

I ended up redoing the config and package resolution for v0.7.x so this is handled automatically and will be addressed with v0.7.0.

I've also decided to make this behavior the only behavior rather than a configurable one as it shouldn't affect most projects and for monorepos things should just work better automatically.