Akrida will not build due to Credo/Node dependency issue

[loneil]

At this time we can't build Akrida because the image it generates pulls up-to-date NodeJS versions. And something in Akrida has broken due to a recent Node Update.

The base Akrida image pulls node 18.x and the issue appears to have cropped up with v18.20.0. (version 20 has the same problem that happened at the same time)

See details on Credo problem here https://github.com/openwallet-foundation/credo-ts/pull/1821

I believe this will be temporary until the Credo change is merged but in the mean time I fix this locally by pinning the Node version to pre-18.20. There's probably a few ways to do this but I'm getting around it by using a pinned base image

[loneil]

Also as per my screenshot above, wondering if there's an advantage to using that Ubuntu image and installing node with curl/apt-get over using a Node base image? (I used that Debian bullseye one out of habit, I think it's smaller too)

[loneil]

Credo update doesn't appear to fix this actually (though Credo now builds successfully in newer Node versions after the fix) as Akrida also has the dependency issue due to importing @aries-framework/node

Since the Credo fix for that would be under @credo-ts/node 0.5.x (likely upcoming 0.5.2?) instead we may need to

• do a specific force resolution of @2060.io/ffi-napi 4.0.9
• update imports once @credo-ts/node release happens but that may be a bigger change switching everything over to @credo-ts references and using 0.5.x? https://github.com/hyperledger/aries-akrida/issues/50

[KimEbert42]

Checking build.

[KimEbert42]

@loneil I reproduced the issue. I think we should pin to a specific version of ffi-napi for now. We should also look at migrating to credo.

[loneil]

I'll note for clarity it's keeping up to date with the updated fork of ffi-napi (this is what the Credo libraries have done to work with Node updates) created by a Credo contributor https://www.npmjs.com/package/@2060.io/ffi-napi

[KimEbert42]

This appears to work now.