Skip to content
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

Getting "Module did not self-register" error in e2e tests #10

Open
jdgrieco opened this issue May 9, 2024 · 2 comments
Open

Getting "Module did not self-register" error in e2e tests #10

jdgrieco opened this issue May 9, 2024 · 2 comments

Comments

@jdgrieco
Copy link

jdgrieco commented May 9, 2024

I'm getting

Error: Module did not self-register: 'node_modules/cryptian/build/Release/cryptian.node'.
❯ bindings node_modules/bindings/bindings.js:112:48
❯ Object.<anonymous> node_modules/cryptian/dist/index.js:53:41

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_DLOPEN_FAILED' }
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

when I run, E2E Vitest test

Can you help with this?

@tugrul
Copy link
Owner

tugrul commented May 10, 2024

Hi @jdgrieco

Thank you for bringing the compatibility issue with the cryptian module to our attention. Based on your report, it appears that there might be a mismatch between the version of Node.js used to build the cryptian module and the version currently running in your environment. To address this, a straightforward solution is to remove the cryptian module dependency from your project (npm uninstall cryptian) and reinstall it (npm install cryptian). This process often resolves compatibility conflicts between the module and your current Node.js runtime. After reinstalling, please give your project another try to see if the issue persists.

If you encounter any further difficulties or have additional questions, feel free to reach out. We're here to assist you and ensure a smooth experience with the cryptian module.

@jdgrieco
Copy link
Author

Hi @tugrul

Thanks for getting back to me quickly.

I did what you suggested, but unfortunately it didn't work.

I use "nvm", the project currently uses the lts/iron version, but I also tried with the lts/hydrogen version. I also tried removing the node_modules folder and reinstalling all the packages.

None of these attempts worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants