"lmdb/lmdb-win32-arm64
6 days ago — Platform specific binary for lmdb on win32 OS with arm64 architecture. Latest version: 3.5.2, last published: 4 days ago."

Yeah, no. #LMDB is an embedded DB library, intentionally kept under 64KB, so that it can be built statically and *embedded* into each app that uses it. It makes a difference whether you build it for 32bit or 64bit apps, and 32bit or 64bit DBs. You can't just build it once and call it "the platform/system LMDB". Stop doing this.

@hyc I guess it's just for easy installation in Node without having a compiler to recompile the Node C++ addons. I remember it was pain to configure at some point. Similar to Python wheels.
@hyc that is, someone else compiles it for you for all platforms, and then you can just import lmdb from "lmdb" from your scripts.

@dchest yes but it's not that simple, especially on Windows. On Win32 with 32bit CPU arch (x86, arm32) you get 32bit DB support by default, which performs best but can't handle DBs larger than 2GB. You need a non-default config to support 64bit DBs. On 64bit CPU arch (x64, arm64) you might still get 32bit DB support by default because M$ decided sizeof(long) is 4.

So, what are you actually getting when you just "import lmdb" that someone else built for you?

@dchest these cryptocurrency clowns just used "the system LMDB" for their blockchain and it blew up in their faces.

Things like this are why we only distribute source code. We get asked for prebuilt binaries all the time, especially for Windows. But no, that's not how it works. You have to know what you're doing, you have to RTFM and pay attention, and build specifically what you need.