Lachlan Miller

@slavco86 we sure can, it's getting worked on https://github.com/cypress-io/cypress/pull/22862. Are you using SvelteKit? I think Svelte + webpack combo will likely land before the full SvelteKit/Vite integration does.

Cool, maybe you can share your config for everyone else to see :100:

Right, I didn't realise you were on 8.5. Definitely recommend upgrading first! When we release our Svelte support, it'll be with Cypress 10 (latest version) in mind.

Can you share your `cypress.json`? Most likely we are (incorrectly) assuming a `cypress` directory exists at some point. Also, if you are opening Cypress 10.x for the first time, there...

That's strange, we definitely have logic considering the `integrationFolder` set to something other than the default. Here is one of our [test projects](https://github.com/cypress-io/cypress/blob/develop/system-tests/projects/migration-e2e-custom-integration/cypress.json#L2) with a custom `integrationFolder`, for example. Are...

Nothing obviously wrong in debug logs. I do see `pnp.js`. Question... are you using Yarn 3? It seems we have some Yarn 3 issues: https://github.com/cypress-io/cypress/issues/22871. If so, perhaps that is...

Just to clarify - if you make a new project with Cypress 9.x run the examples tests, then update, do you have the same error? Is this problem related to...

I think this is the same as: https://github.com/cypress-io/cypress/issues/22871 https://github.com/cypress-io/cypress/issues/22747 Problem is we use `require.resolve` for many things which assumes the usual Node algorithm to look upwards for `node_modules`. Yarn 2+...

^ That is definitely strange. Any chance you can provide a minimal reproduction? I can't help but think it's a combination of Yarn 2+ with the alternative node_modules resolution or...

It will be fixed in the next release.