Jesse van der Pluijm

I build my own little `util` class if you're interested. I used this class to normalise the configuration for `Dotenv` throughout my app too. ```java import io.github.cdimascio.dotenv.Dotenv; public class Config...

I noticed that the PR that would supposedly implement support for this was closed without merging. Any reason for that?

I've hacked around this a little bit for now. Basically splitting the error string, filtering out duplicates, and whitelisting the error messages I expect / want. But this feels really...

## Example #### To do before merging 📝 - [ ] Update docs - [ ] Etc.

Hi. I looked at this one afternoon after I submitted this issue. But I couldn’t quickly make sense of where to add this. (Messing with someone elses code base always...

I definitely am. Since GitHub implemented draft PR's which offer a lot of the same functionality, this would be a great feature to go beyond what is natively offered already....

Thanks for your quick response! Unfortunately I can't share my full repo. I might have time to setup a minimal reproduction repo later this week. For now, here's the most...

It seems `config/vite.json` is a file used by [Vite Ruby](https://vite-ruby.netlify.app) (see [configuration](https://vite-ruby.netlify.app/config/)). I strongly suspect that the issue has something to do with the full paths being used by Cypress...

@lmiller1990 did you replicate the issue with success? Do you also see the same 404 server output in your terminal? ``` GET /__cypress/iframes//Users///cypress/component/example.cy.js 404 2.497 ms - - ``` Could...

Have you had any success narrowing down the issue? I don't quite get how my Vite configuration should impact the path that Cypress uses to attempt to GET my spec...