Ari Perkkiö

I guess this feature request is coming from `esbuild`'s and `terser`'s behavior. With those two you could just use `/* istanbul ignore -- @preserve */`. ```diff -/* istanbul ignore if...

Before the upstream issue is resolved I don't think anything should be done to `@cypress/code-coverage` codebase. As work-around you should be able to place a `.nycrc` next to `cypress.config.ts` and...

@davetapley were you able to run this using the default free-tier of Codespaces, the `4 core • 8GB RAM • 32GB` option? Is your configured repository open source? I'm running...

Got it working now based on your instructions @davetapley! I'm finally able to run Cypress on my Chromebook. I ended up documenting a minimal setup into https://github.com/AriPerkkio/cypress-codespaces-example.

@petermarcoen even if `getByRole('status', { name: 'Status message' })` query would work you might not want to use it. Querying `role="status"` containers directly with their content easily leads to false...

It's not only happening in source control tab. I'm seeing these differences in all files. Typescript definitions are now also italic/recursive. Is this intended? Especially the `React.FC` part looks weird....

Thanks for the improvement idea and sorry for breaking your tests @voxpelli. Ignoring the inline configurations is indeed intended default functionality of `eslint-remote-tester` but I'm open for allowing overriding it...

Using container is a good idea. Just to clarify - the tool itself does not download untrusted code at all. It only downloads the repositories which it is configured to....

I think support from `c8` is required as well: https://github.com/bcoe/c8/pull/415 Istanbul provider is already passing the `ctx.config.root` to `test-exclude`. https://github.com/vitest-dev/vitest/blob/88d5764894f62449540209567df19926e46a91f3/packages/coverage-istanbul/src/provider.ts#L61-L67

Looks like `c8` has an undocumented `resolve` option which might solve this. https://github.com/bcoe/c8/blob/7f1069dcce6821a6794557b39d6a13f620c64bad/lib/parse-args.js#L136-L139 @alexlafroscia I've tried to reproduce this issue using the reproduction repository. However I'm not seeing the expected...