Mike McCready

According to https://vite.dev/guide/rolldown.html#reporting-issues > Since this is an experimental integration, you may encounter issues. https://vite.dev/guide/rolldown.html#future-plans > The rolldown-vite package is a temporary solution to gather feedback and stabilize the Rolldown...

@eMerzh > Yeah rolldown is experminental at this point, but it feels that here the issue lies within cypress, and it's a hint that it wont be compatible with the...

Vite announced [Vite 8 Beta: The Rolldown-powered Vite](https://vite.dev/blog/announcing-vite8-beta) on Dec 3, 2025.

- See also https://github.com/cypress-io/cypress/issues/33078

@bmulholland Sorry that the workaround was left in this issue! I have commented it out now. I suggest you benchmark your original configuration and then measure the timing after you...

@bmulholland > pnpm install without a cache takes about a minute. With a cache takes about half that. Good to have the measurements! > I'm paying for Cypress.io, and want...

@bmulholland / @jennifer-shehane - The intention of this enhancement request (https://github.com/cypress-io/github-action/issues/1044) is to provide built-in support for pnpm caching in the `cypress-io/github-action`. The recent discussion is however about doing this...

- Due to pnpm issue https://github.com/pnpm/pnpm/issues/9123 , if the pnpm Store is cached, `pnpm install` can fail to run the Cypress postinstall script. The workaround would be to always run...

I have now learned that the project `.npmrc` for pnpm with Cypress needs to include: ```text side-effects-cache=false ``` See https://pnpm.io/npmrc#side-effects-cache Edit: This is now added to the documentation and example

- This request is replaced by #1366 which takes a higher-level view of package manager caching in the action.