Change Details

- poudriere -> OK (12.3-, 13.1-RELEASE, 14.0-CURRENT@8c309d48aab amd64) - dogfooding -> Runs fine, synchronizing with AnkiWeb works as expected. - If someone(tm) can run a test build on a aarch64 Platform that would be great as I don't own a native arm64 platform at the moment. Next steps: - If approved, commit `devel/esbuild-anki` separately and add the `CONFLICTS_INSTALL` line to `devel/esbuild` afterwards. NB: Since the Anki 2.1.50 release Qt6 is also supported and should give us additional playgrounds to test `qt6-webengine` (once there's a review, still heavy WIP) Rationale for adding `devel/esbuild-anki`: The Bazel rule for NodeJS, which is used by Anki in this release, uses the 0.14.11 NPM release of `esbuild`. The JS part of `esbuild` has a strict version check and wants exactly the same release for the binary version, see also https://github.com/evanw/esbuild/blob/v0.15.6/lib/shared/common.ts#L668 Patching doesn't seem to work: - If the affected line is patched via the Ports framework during build Bazel automatically reloads the unpatched/untampered version from its cache. - Using `postinstall: "patch-package"` in the `package.json` for the esbuild toolchain doesn't work either. This method seems to work only if the esbuild toolchain is fetched online and not using the offline-cache.

- poudriere -> OK (12.3-, 13.1-RELEASE, 14.0-CURRENT@8c309d48aab amd64) - dogfooding -> Runs fine, synchronizing with AnkiWeb works as expected. - If someone(tm) can run a test build on a aarch64 Platform that would be great as I don't own a native arm64 platform at the moment. NB: Since the Anki 2.1.50 release Qt6 is also supported and should give us additional playgrounds to test `qt6-webengine` (once there's a review, still heavy WIP)

- poudriere -> OK (12.3-, 13.1-RELEASE, 14.0-CURRENT@8c309d48aab amd64) - dogfooding -> Runs fine, synchronizing with AnkiWeb works as expected. - If someone(tm) can run a test build on a aarch64 Platform that would be great as I don't own a native arm64 platform at the moment. Next steps: - If approved, commit `devel/esbuild-anki` separately and add the `CONFLICTS_INSTALL` line to `devel/esbuild` afterwards. NB: Since the Anki 2.1.50 release Qt6 is also supported and should give us additional playgrounds to test `qt6-webengine` (once there's a review, still heavy WIP) Rationale for adding `devel/esbuild-anki`: The Bazel rule for NodeJS, which is used by Anki in this release, uses the 0.14.11 NPM release of `esbuild`. The JS part of `esbuild` has a strict version check and wants exactly the same release for the binary version, see also https://github.com/evanw/esbuild/blob/v0.15.6/lib/shared/common.ts#L668 Patching doesn't seem to work: - If the affected line is patched via the Ports framework during build Bazel automatically reloads the unpatched/untampered version from its cache. - Using `postinstall: "patch-package"` in the `package.json` for the esbuild toolchain doesn't work either. This method seems to work only if the esbuild toolchain is fetched online and not using the offline-cache.