Phil Ricketts
Phil Ricketts
During my new Angular project I will evaluate how difficult it would be to implement a similar `jsdom` browserless angular component unit testing project into Playwright, removing Vitest completely. I...
## playwright single-framework tradeoffs I have done some investigations and discovered significant tradeoffs with my 'one testing framework' idea: **Pros:** - Single framework for unit/API/integration/E2E/a11y/perf tests - Fewer dependencies, simpler...
@joematthews Somehow I completely missed that. I pushed a commit to the playwright branch that places the artifact folders into `./.playwright`. A bit tidier. Interesting tradeoffs with a starter template,...
@karcherm Thanks for the info. I read the angular cli source and can see the issue, it's an angular bug. I have added a workaround, but I do not have...
@jelovac I went with something else in my project as this felt like it could be a problematic dependency situation and unsuitable for my needs
Reinstalled Quiet Outline 0.4.3, macOS Looks fine here? What OS? Also make sure Obsidian `Installer Version` is recently up to date. If the installer version is too far behind, some...
@hsandt Is this still a problem?
Okay cool, thanks for the ghost
I did consider that it would be relatively straightforward to pipe in a per-file score to my ESLint configuration, but then wondered how useful it would be in the IDE...
I spent a lot of time trying to make this work with the Vitest VSCode `vitest.explorer` extension, as mentioned earlier trying to get the AnalogJS plugin working, which adds undesired...