Cannot run component testing in pre-commit hook

Current behavior

If I add “npx cypress run-ct” in .git/pre-commit and use default vs code git GUI to make a commit I get an error:

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -

> template@1.0.0 pre-commit
> npm run test-ci


> template@1.0.0 test-ci
> cross-env NODE_ENV=development cypress run-ct

We found an invalid configuration value:

Found an error while validating the `browsers` list. Expected `version` to be a non-empty string. Instead the value was: `{"name":"electron","channel":"stable","family":"chromium","displayName":"Electron","version":"","path":"","info":"Electron is the default browser that comes with Cypress. This is the default browser that runs in headless mode. Selecting this browser is useful when debugging. The version number indicates the underlying Chromium version that Electron uses."}`
husky - pre-commit hook exited with code 1 (error)

Desired behavior

The hook runs with no errors

Test code to reproduce

I added husky to make it easier to run hooks (the problem can be reproduced without it)

How to reproduce:

1. Clone Repo
2. npm i
3. npm set-script new “cypress run-ct” # make changes to repo
4. use vs code (version 1.59, all extensions disabled) to commit changes and click “Show command output”

Cypress Version

8.2.0

Other

If I change cypress version to 7.7.0 the error changes to something like this: “Cannot import module “–run-project”” If I run another command e.g. open-ct it succeeds If I commit without using VS Code git GUI then the hook with run-ct succeeds

[a-zich]

I run into the same problem in VSCode. As @jennifer-shehane asked about the environment variables, I added an ‘export’ command before the test run. And yes, besided a lot of other stuff, it shows

export ELECTRON_RUN_AS_NODE=“1”

So VSCode sets this automatically.

I change my pre_commit file and it commited fine.

echo "***Running unit tests***"
unset ELECTRON_RUN_AS_NODE
npm test -- --config video=false screenshotOnRunFailure=false

[Omarov3000]

I experience the same problem on MacOS. I have the similar log as @JessicaSachs has.