cache/hashing is unclear and will invalidate caching on projects that do not have `node` dependencies about nx HOT 3 OPEN

@AgentEnder @juristr is there something wrong at my understanding the Mental Model using external dependencies like dotnet and inputs? if so, how should the documentation reflect that?
We'd like to generalize the affected command in our workflows and not needing to use the exclude parameter to work around this issue. That'd defeat the purpose of this whole setup

from nx.

I've been able to pinpoint it a little more closely for a more real-life scenario at https://github.com/EelcoLos/nx-tinkering .
So, the main branch has nx 19.5.0 . I installed all the packages and ran npx nx run-many -t build test on there.
Then i created a branch test-package-lock-dotnet, where I first tried the case above. This already showed the projects api-demo and api-demo.Test to be affected.
When running npx nx affected -t build test at that point (which is EelcoLos/nx-tinkering@3416d7d), the items are affected. However, the cache states there is a local cache hit.

So, upon pointing out a more real life scenario, I updated all npm packages today resulting in EelcoLos/nx-tinkering#2 .
This did trigger the cache to be void, even for api-demo and api-demo.Test.
My guess at this point (with some testing of my own) is that affecting dependencies (not devDependencies) trigger the cache to be void

from nx.

I'm also hoping to get to know how to create your own hasher with a plugin. I'd like to create a plugin using a language not using node as well :)

from nx.