`--config` changes working directory, Cypress 9 -> 10/11/12

Current behavior

In after:run task, Cypress 10 is using the location of configuration file as current working directory. In Cypress 9 it is the root of project, or where the actual cypress run command is run.

After migrating from Cypress 9 to 10 some plugins I’m using started failing. They are relying on Cypress 9’s functionality when it comes to current working directory, e.g. when reading files from disk.

I keep my cypress.config.ts in a separate folder - not in the project root.

/workspaces/vite-everything
└── config
   └── cypress
      ├── component-index.html
      ├── cypress.config.ts
      ├── support.component.ts
      └── support.ts

cypress run --component --config-file config/cypress/cypress.config.ts

// config/cypress/cypress.config.ts
setupNodeEvents(on) {
    on('after:run', () => {
        console.log('[after:run] cwd is', process.cwd());
        // > [after:run] cwd is /workspaces/vite-everything/config/cypress
    });
},

Desired behavior

The current working directory should match with Cypress 9.

/workspaces/vite-everything
└── config
   └── cypress
      ├── cypress.json
      ├── plugins.ts
      └── support.ts

cypress run-ct --config-file config/cypress/cypress.json

// config/cypress/plugins.ts
on('after:run', () => {
    console.log('[after:run] cwd is', process.cwd());
    // [after:run] cwd is /workspaces/vite-everything
});

Test code to reproduce

I run into this error in separate closed source project but here is another project for reproducing the issue:

• https://github.com/AriPerkkio/vite-everything
• Branch test/cypress-9-after-run-cwd for previous functionality: https://github.com/AriPerkkio/vite-everything/commit/0e282c86eefa3766f25b374f5562518e6ecce3db
• Branch test/cypress-10-after-run-cwd for current funcionality: https://github.com/AriPerkkio/vite-everything/commit/dbead4b1c90a107f2dbea6cbea454d3ccc89e5da

yarn # Install dependencies
yarn test:component # Run Cypress Component Test Runner

Cypress Version

10.3.0

Other

No response

[AriPerkkio]

@gsouf that’s best solution for now.

I really want to keep Cypress configuration file under a sub directory config/ since that’s where I store configuration files for all sorts of tooling. So as a work-around I’m now using a separate configuration file in project root which simply imports the actual config. This way I don’t need to apply any other work-arounds, e.g. prefixing all paths with .../../ or running process.chdir() anywhere.

<project-root>
├── cypress.config.ts
└── config
   └── cypress
      └── cypress.config.ts

// TODO: Remove when https://github.com/cypress-io/cypress/issues/22689 is fixed
export { default } from './config/cypress/cypress.config';

[gsouf]

@jhpedemonte maybe it is simpler to keep the config file at the root until this is fixed?