Prisma might have renamed their query engines?

[RoccoFarrell]

Line 52 of the generate.js script has

const engineFile = (0, fs_1.readdirSync)(clientPath).find((f) => f.startsWith('libquery_engine-'));

where clientPath is .\node_modules\@prismany\client\base_schema

However the copied engine is named query_engine-windows.dll.node

Changing line 52 to const engineFile = (0, fs_1.readdirSync)(clientPath).find((f) => f.startsWith('query_engine-')); allows the script to fi nish

[JoeRoddy]

hmmmm, thanks for opening this @RoccoFarrell

I'm guessing you're right about the reason, I would say for now, if you really need this library, you would need to downgrade your Prisma version, or fork it with the change you suggested. I know that's not a satisfying answer. Just don't have time to test your change on all Os's.

I'm wrapping up a big leg of a project right now, but once I'm done that I can look into this. Probably a few weeks.

[JoeRoddy]

It's also possible it's a windows specific issue, I've never tested this library on Windows, so it's possible it was always broken there.