Hi @nathanhammond

Thanks for replying. Unfortunately specifying inputs outside the package directory doesn't work.

I actually opened opened a feature request issue for this at #1064 which details why a shareable configuration in a package isn't a great solution for this kind of dependencies.

I found what may be the issue and would be treated as a bug. I'll get back to you after I poke at it for a bit.

i just run into this eslint config issue. I reported a bug (I misunderstood how pipelines work; turbo is ok) but imo turbo+eslint deserves more examples/better default configuration in npx create-turbo script. I find a solution where I use global dependencies to miss cache when eslint package changes.

Trying to make use of this feature in a large monorepo where we have packages at various levels of depth from the root of the repo.
e.g.,

.eslintrc
/server
  package.json
/packages
  /shared-package-1
    package.json
/client
  /apps
    /app-1
      package.json
    /app-2
      package.json

Is there any way to specify inputs relative to the repo root, instead of the package?

e.g., if each package has a lint command, and they all extend the .eslintrc that lives at the repo root. The path to this root .eslintrc is different depending on how deep the packages is, so using something like ../../.eslintrc wouldn't work.

Tried the following, which did not work:

{
  "$schema": "https://turborepo.org/schema.json",
  "pipeline": {
    "lint": {
      "inputs": [
        "/.eslintrc.js", // <-- how to specify this is from repo root and not relative to the package?
        "src/**"
      ]
    }
  }
}

would encourage you to create a package with a shareable configuration for your ESLint rules and then pass that package in to extends in your .eslintrc.js

@nathanhammond i have exactly this setup and turbo is not busting the cache when i change a rule in the shareable config. for context the config package is a workspace:* dep. it seems maybe turbo is never busting the cache for any of these workspace deps actually. should i file a bug?