Task runner works fine.
Task runner does not work
I updated an existing nx workspace from 8.x to 9.1.0. Now i cannot run any task.
The option for caching is set in the nx.json
"tasksRunnerOptions": {
"default": {
"runner": "@nrwl/workspace/src/tasks-runner/tasks-runner-v2",
"options": {
"cacheableOperations": ["build", "test", "lint"]
}
}
}
With runner v2 there is the error (See below). With task runner v1 it works fine. But i think then the caching doesn't work, but that's fine.
> NX Report complete - copy this into the issue template
@nrwl/angular : 9.1.1
@nrwl/cli : 9.1.1
@nrwl/cypress : 9.1.1
@nrwl/eslint-plugin-nx : Not Found
@nrwl/express : Not Found
@nrwl/jest : 9.1.1
@nrwl/linter : Not Found
@nrwl/nest : Not Found
@nrwl/next : Not Found
@nrwl/node : Not Found
@nrwl/react : Not Found
@nrwl/schematics : Not Found
@nrwl/tao : 9.1.1
@nrwl/web : Not Found
@nrwl/workspace : 9.1.1
typescript : 3.7.5
runner undefined
nxJson.tasksRunnerOptions {
default: {
runner: '@nrwl/workspace/src/tasks-runner/tasks-runner-v2',
options: { cacheableOperations: [Array] }
}
}
tasksRunner { tasksRunnerV2: [Function] } object
(node:23884) UnhandledPromiseRejectionWarning: TypeError: tasksRunner is not a function
at Object.<anonymous> (/Users/pitti/web/actaport-ui v9/node_modules/@nrwl/workspace/src/tasks-runner/run-command.js:37:9)
at Generator.next (<anonymous>)
at fulfilled (/Users/pitti/web/actaport-ui v9/node_modules/@nrwl/workspace/src/tasks-runner/run-command.js:5:58)
(node:23884) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:23884) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Thanks for reporting this issue! Sorry for the inconvenience.
We will have a fix shortly.
Wow. That was a fast fix. Thx a lot.