Ari Perkkiö
Ari Perkkiö
The bug is still there. Tested locally on MacOS with `Node.js v22.13.1`. Reproduces also on: - https://stackblitz.com/~/edit/eslint-exit-on-crash-9-19?file=index.mjs - https://github.com/AriPerkkio/eslint-remote-tester/pull/569
I think the example from @fasttime requires argument for `lintFiles`. It wouldn't crash on my setup without it too. This makes it crash: ```diff try { - await linter.lintFiles(); +...
Fix verified on `[email protected]` - thanks! - https://github.com/AriPerkkio/eslint-remote-tester/pull/569
As said before, in order to use coverage for this we would first need to run all tests so that we have coverage results. That kind of breaks the intention...
Yup that would be great! If `'Debugger.setBreakpointByUrl'` with `{ lineNumber: 0 }` doesn't work automatically, we might need to get breakpoints with `Debugger.getPossibleBreakpoints` first.
This seems to consider all usage of `react-resizable-panels`. When fixing this, make sure to check codebase for `// TODO: Requires #245` comments and fix those as well.
Showing diff for the currently open file should be quite easy to do. All we need is to somehow compute the diff of two files in browser, and add `diff`...
Sounds good! I didn't really like #212 and #256 as those added language specific features for all users. Some users may not be interested in Svelte at all, but they'll...
As work-around for now you can set `coverage.all: false` or configure Svelte plugin in the root `vitest.config.ts`. I think this is caused by the root `vitest.config.ts` not having Svelte Vite...