we have a very similar setup. some packages with webpack. it was difficult generating coverage for each of this sub packages. we wanted all source files, including untested ones, to be instrumented. moving to single cypress setup with v10.

Thanks! This is great to know. How did you handle having multiple webpack configs? From what I've seen in the examples, there's only ever one being passed in https://docs.cypress.io/guides/component-testing/component-framework-configuration#React-with-Webpack

hey Liam. we are using 1 dedicated webpack config for test runner. instead of reusing the webpack config that we use for our build generation

Oh that's a neat way of approaching it!

yeah we have a messy setup :p trying to get around that. also coverage for us is a must. its still work in progress but we are going with this.

Really useful to know. Thanks!