-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix problem of Colleagues from Fujitsu #111
Comments
This issue is partially solved with the latest packages publish. In CJS mode it works just fine. That means, in tsc
node .
However, pure ESM mode is not working yet. That means, the following will fail: tsc --module esnext
mv dist/index.js dist/index.mjs
node dist/index.mjs The error:
I am in the process of fixing |
Finally, JS SDK works in ESM with the following packages versions: {
"@iroha2/client": "^2.0.2",
"@iroha2/crypto-core": "^0.1.1",
"@iroha2/crypto-target-node": "^0.4.0",
"@iroha2/data-model": "^2.0.2"
} Now it is possible to run the following without getting ESM/CJS errors: rm -r dist
pnpm tsc
mv dist/index.js dist/index.mjs
node dist/index.mjs |
Our colleagues from Fujitsu have asked us to provide assistance in setting up their Iroha interoperability. Their work can be found here.
https://github.com/outSH/iroha2_check
@0x009922, @antyas mentioned that you are working on something similar.
The text was updated successfully, but these errors were encountered: