yarn add detox-cli --dev
yarn run detox
This results in:
node_modules/.bin/detox: fork: Resource temporarily unavailable
I appreciate this might be something local to my machine, but is there any reason why this general approach wouldn't work?
detox-cli is a convenience module, it should be installed globally to be available for as a binary in your command line.
yarn global add detox-cli
It wraps the binaries under detox/local-cli and just executes them.
You can either install it globally and get the benefit of calling detox from command line:
detox test
or don't use it at all and call the detox from your node modules:
./node_mmodules/.bin/detox test
Gotcha, thanks.
Most helpful comment
detox-cli is a convenience module, it should be installed globally to be available for as a binary in your command line.
yarn global add detox-cliIt wraps the binaries under detox/local-cli and just executes them.
You can either install it globally and get the benefit of calling detox from command line:
detox testor don't use it at all and call the detox from your node modules:
./node_mmodules/.bin/detox test