Current Behavior

Overall setup : in my monorepo, I have a code-generator tool (let’s call it codegen). Some other projects use it to generate some code. Obviously, I want changes in codegen to result in the "codegen" task in the projects to be re-run. To achieve that behavior, I’m defining this in targetDefaults :

        "codegen": {
            "cache": true,
            "dependsOn": [{"projects": ["codegen"], "target": "build"}],
            "inputs": [{"dependentTasksOutputFiles": "**/*.js", "transitive": false}],
            "outputs": ["{projectRoot}/gen/**/*"]
        }

(build is standard, takes src/**/*.ts as input, output is dist/**/*.js)

If I run nx run project:codegen, then do some chage to codegen, then re-run nx run project:codegen, the behavior depends on the value of NX_NATIVE_TASK_HASHER :

• If unset, the second codegen run will reuse cache
• If set to false, the second codegen run will NOT reuse cache

Expected Behavior

Unless I did a mistake, it should not reuse cache in both cases. Even if I made a mistake somewhere, the two behaviors should match.

GitHub Repo

https://github.com/sloonz/nx-hasher-issue-repo

Steps to Reproduce

In the example repository, run nx run project:codegen, then do some change to codegen/src/main.ts (just increment the counter), the re-run nx run project:codegen.

Nx Report

NX   Report complete - copy this into the issue template

Node   : 21.7.0
OS     : linux-x64
npm    : 10.5.0

nx             : 18.0.8
@nx/workspace  : 18.0.8
@nx/devkit     : 18.0.8
@nrwl/tao      : 18.0.8
typescript     : 5.4.2

Failure Logs

No response

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response