Christian Ulbrich

Your best bet is, to simply run your WebPack build before running the tests, as @LarsDenBakker has suggested. That way you have one build toolchain. For unit tests this can...

@trusktr I am allergic to submodules. Just kidding. One mono repo managed by `pnpm`. I think the problem is pretty obvious, but apparently not so easy to be solved -...

@rlnas @gethari I do not know your build stack. The OP had Webpack in place. Things are a lot more different, than they used to be in 2021. _Nowadays_ I'd...

@gethari There is no easy way I am afraid. If this is for a commercial project, I'd gladly offer consulting service; this is something, that at least takes 2-3 days......

Just to chime in a little bit on adding some insights, why your tests might fail on CI and seem to be flaky (or blaming Playwright for that matter) -...

I prepared two PRs, which would be **my** suggestions. I do not have a very strong preference, but **I** think, that #252 would be the _better_ choice. Ultimately @tiangolo is...

I would not bother setting up a complete cross-compiler chain. Simply use Docker _locally_ and build directly against `public.ecr.aws/amazonlinux/amazonlinux:latest`, that way you get all the benefits: * _multi-arch_ - build,...

This is a bug. It happens, because of the comma in the codecs _parameter value_. Having dived way too deep into RFCs and standards, it seems that _comma-separated_ **_values_** for...

@manuel-mauky While I also do not know your codebase, your installed version of `eslint` (and probably also the version of `typescript-eslint` and for that matter, the used version of `typescript`...