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

Bug report: Node API breaks on crypto-api import #596

Open
n1474335 opened this issue Jul 9, 2019 · 3 comments · May be fixed by masifpak/CyberChef#7, Croat79/CyberChef#8 or Centaurioun/CyberChef#33
Open
Assignees
Labels

Comments

@n1474335
Copy link
Member

n1474335 commented Jul 9, 2019

Issue raised on crypto-api repo to fix: nf404/crypto-api#12

@n1474335 n1474335 added the bug label Jul 9, 2019
@n1474335 n1474335 self-assigned this Jul 9, 2019
@d98762625
Copy link
Member

The current release of the Node API is only tested against Node LTS, so v10.13.0. We need that crypto-api fix to make it compatible with other versions, but I'll document valid versions of Node somewhere

@d98762625
Copy link
Member

I'll correct myself: the current cyberchef release throws the same ERR_REQUIRE_ESM error if you require it.

There is a workaround if the consuming application uses esm, which is to import the source index:

import chef from "cyberchef/src/node/index"

I assume that conforms with what you experienced?

@d98762625
Copy link
Member

After #600 was merged you should now be able to use top-level imports up to and including node v12. Named imports still do not work with v12 for the same reason we got before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment