As of Nx 20, the tasksRunnerOptions property in nx.json is deprecated

[kmaraz]

As it is announced in the Nx documentation, the tasksRunnerOptions property in nx.json is deprecated. Is there any future for this amazing project in this case? Would it be possible to use it with the Nx21 onward?

Thank you!

[el-davo]

The question was also posted here - https://github.com/nrwl/nx/discussions/28332

[robinpellegrims]

The announced deprecation of custom caching solutions in Nx 21+ represents a significant shift that will impact all packages relying on nx-remotecache-custom. This decision has raised concerns within the community, prompting discussions about potential alternatives and the future of custom caching in Nx. To participate in this important conversation, please join the conversation there.

We are closely monitoring the situation and any solutions that emerge from the community. If a viable option to maintain compatibility with Nx 21+ arises, we will implement it to ensure the continued functionality of nx-remotecache-s3.

For further context, Nx has addressed the community's feedback regarding this questionable change in the following thread: link to Nx response.

[Jordan-Hall]

If it helps i'm working on a nx core fork that will also wrap all nx calls to the fork so nothing breaks but add supports for remote caching.

I can provide docs on getting it working. SHould be easy to migrate the pacakge will add a post install script to decorate the nx command to use the fork.

You can see the API change here https://github.com/Jordan-Hall/onx-core/pull/3

[charlesanim]

@Jordan-Hall Thanks for all the effort on this. Following