Runtime issue related to using credo from ESM project

[Patrik-Stas]

Creating isolated issue for issue discovered as part of #2579

When project is using ESM modules and credo, it leads to runtime issues.

For reproduction checkout commit 13df6845bc4dc8c1671bf00698deed1658d10473 from repo https://github.com/Patrik-Stas/tsx-credo-06-reproduction/tree/main

If you run pnpm run test you should see in output

[ERROR] DID not created, didCreateResult: {
  "didDocumentMetadata": {},
  "didRegistrationMetadata": {},
  "didState": {
    "state": "failed",
    "reason": "unknownError: Error creating key"
  }
}
[ERROR] ❌ Script failed with error

but if you remove type: module it will succeed

[INFO] ✅ DID key created successfully
[INFO]   DID: did:key:z6MkfnXzhM8iivsgd9774ZHCqKcXDkBEVnY9jwb2BQUFWqfH
[INFO]   KID: did:key:z6MkfnXzhM8iivsgd9774ZHCqKcXDkBEVnY9jwb2BQUFWqfH#z6MkfnXzhM8iivsgd9774ZHCqKcXDkBEVnY9jwb2BQUFWqfH
[INFO] ✅ Script completed successfully

The repo is using simplest possible agent

    const agent = new Agent({
      config: {
        logger: new SimpleLogger(logLevel),
      },
      dependencies: agentDependencies,
      modules: {
        askar: new AskarModule({
          askar: askar,
          store: {
            id: walletId,
            key: walletKey,
          },
          enableKms: true,
          enableStorage: true, // Use Askar's default SQLite storage
        }),
      },
    });

[TimoGlastra]

Hi @Patrik-Stas,

I think this issue is caused by ##2597.

Somehow ESM makes the registration of Askar work differently. For now I can make your repo work by adding the import of Askar nodejs to the top of the file.

Generally we throw error and the full stack trace would show this, but we don't log the error in the key did registrar. We should change that.

We are about to release Askar wrapper 0.5.x, which has a fix for this. But there's still some issues with the new FFI library we're using.

[genaris]

We are about to release Askar wrapper 0.5.x, which has a fix for this. But there's still some issues with the new FFI library we're using.

Oh! What issues are you referring to?