Frank Harrison

> Yeah, the only issue is that the current design makes the Checker level not really sufficient for splitting the work into processes 😅 Going back a few steps, this...

As noted above the install is trying to incorrectly link against the `/usr/local` intel variant of the lib and not the `/opt/local` arm64 variant. This happens same error happens with...

Still the same. Looking at it with fresh eyes, the issue is upstream in [libffi's](https://github.com/libffi/libffi) python module, which just needs to add the relevant rpath to the module. If I...

tldr; works with a clean env. It looks like my env was dirty and still had the old backend dylib, so it is working, with caveats. Luckily I still had...

Done. The conflict was with the instruction to auto-install hooks on `npm install`: `npm set-script prepare "husky install"` -> `npm pkg set scripts.prepare="husky install"` I've replaced all three places that...

I removed it. Whilst trying to understand the (very poorly structured) feedback I found a few issues that required some more work, so because it polluted the main purpose of...

That's a good suggestion.

Try adding `-x` to the `sh -e "$0" "$@"` line. This will enable tracing mode. So make it look like: `sh -x -e "$0" "$@"`

This still needs consideration.

> So which one is the correct README.md to follow, and most up to date??? Exactly! I’ve had PR #1167 open for a long time, but this project seems to...