You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting CI=true start jest in non-interactive mode but without colors because most tools only check wether or not the CI environment variables exist an not it's value: https://github.com/watson/ci-info/blob/master/index.js#L53
Because of this you loose some functionalities, like colors when using tools like np or lerna.
Desired Behavior
Being able to run tsdx test in non-interactive way without setting the CI variable.
Suggested Solution
Using a different environment variable name to disable "auto watch mode":
TSDX_AUTO_WATCH=false tsdx test
Who does this impact? Who is this for?
This impact everyone who was using tsdx test in non-interactive mode outside of a CI.
It would make the migration from 0.11 to 0.12 easier.
The text was updated successfully, but these errors were encountered:
Current Behavior
yarn test
start jest in interactive modeCI=true
start jest in non-interactive mode but without colors because most tools only check wether or not theCI
environment variables exist an not it's value:https://github.com/watson/ci-info/blob/master/index.js#L53
Because of this you loose some functionalities, like colors when using tools like
np
orlerna
.Desired Behavior
Being able to run
tsdx test
in non-interactive way without setting theCI
variable.Suggested Solution
Using a different environment variable name to disable "auto watch mode":
Who does this impact? Who is this for?
This impact everyone who was using
tsdx test
in non-interactive mode outside of a CI.It would make the migration from
0.11
to0.12
easier.The text was updated successfully, but these errors were encountered: