https://github.com/dmitry-stepanenko/nx-named-inputs-invalid-cache
https://github.com/dmitry-stepanenko/nx-named-inputs-invalid-cache
Last synced: about 1 month ago
JSON representation
- Host: GitHub
- URL: https://github.com/dmitry-stepanenko/nx-named-inputs-invalid-cache
- Owner: dmitry-stepanenko
- Created: 2023-10-02T06:29:45.000Z (over 2 years ago)
- Default Branch: main
- Last Pushed: 2023-10-02T10:51:00.000Z (over 2 years ago)
- Last Synced: 2025-02-28T23:59:01.461Z (over 1 year ago)
- Language: TypeScript
- Size: 326 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
This repository is configured to have a `"someDynamicValues": [ { "runtime": "node log.js" } ]` namedInput for build tasks. Looks like Nx Daemon ignores this input.
To reproduce the issue:
1. Make sure `tasksRunnerOptions.default.options.useDaemonProcess` in nx.json is set to `false`
2. Run `nx reset && nx build myapp && MY_VAR=123 nx build myapp`
3. Notice that there're no cache hits and `console.log`s in build outputs are different (`MY_VAR IS undefined` and `MY_VAR IS 123`)
4. Set `tasksRunnerOptions.default.options.useDaemonProcess` to `true`
5. Run command from the step 2 again
6. Notice the cache hit for the second run. That's not expected.