Can Jest use npm_lifecycle_script to determine the update command?

[adityavohra7]

Do you want to request a feature or report a bug?
Feature!

What is the current behavior?
Jest uses process.env.npm_lifecycle_event to determine what the command to update snapshots should be. It feels like Jest is assuming that the lifecycle script invokes Jest directly?

What is the expected behavior?
Could Jest use process.env.npm_lifecycle_script to confirm that the lifecycle script invokes Jest directly. If it does, keep the current behavior, if it doesn't, try to guess a better update command? The motivation is a use case wherein people are wrapping the Jest invocation in some script.

Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.

$ ./node_modules/.bin/jest --version
v20.0.4

$ node --version
v8.4.0

$ npm --version
5.3.0

$ uname -a
Linux dev9-uswest1cdevc 4.2.0-42-generic #49~14.04.1-Ubuntu SMP Wed Jun 29 20:22:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

[cpojer]

You can try sending a PR for that :)

[adityavohra7]

Sure! I'll give it a shot 😊

I'll try to get this PR merged first 😀

[thymikee]

This also needs to be updated: #4468

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.