-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Bug report: Node API breaks on crypto-api import #596
Comments
The current release of the Node API is only tested against Node LTS, so v10.13.0. We need that |
I'll correct myself: the current There is a workaround if the consuming application uses import chef from "cyberchef/src/node/index" I assume that conforms with what you experienced? |
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. |
Issue raised on crypto-api repo to fix: nf404/crypto-api#12
The text was updated successfully, but these errors were encountered: