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: Development does not work with current LTS (Node.js 12) #1002

Closed
Prinzhorn opened this issue Mar 30, 2020 · 3 comments
Closed

Bug report: Development does not work with current LTS (Node.js 12) #1002

Prinzhorn opened this issue Mar 30, 2020 · 3 comments
Labels

Comments

@Prinzhorn
Copy link
Contributor

Describe the bug

This is already known (#575, #662) but there is no issue to track this. More importantly https://github.com/gchq/CyberChef/wiki/Getting-started still says

Install the latest LTS version of Node.js and its package manager, npm

which is wrong. I guess I don't have permission to edit the wiki, so updating this would save people like me some time in the future.

To Reproduce

Follow Getting Started with latest LTS (Node 12 not 10) and see grunt dev crash due to mjs stuff.

Expected behaviour

It should work with "the latest LTS version of Node.js". In the mean time the Wiki needs to be updated.

Additional context

@n1474335 says

Yes, you must be using the current Node LTS to build CyberChef. There are some dependencies that don't support Node 12 yet. We'll update them as soon as they are fixed.

But which dependencies exactly are affected? Where is this tracked? I know of "crypto-api", PR is here nf404/crypto-api#12

@Prinzhorn Prinzhorn added the bug label Mar 30, 2020
@n1073645
Copy link
Contributor

It has been modified.

@Prinzhorn
Copy link
Contributor Author

Thank you

@mt3571
Copy link
Contributor

mt3571 commented Dec 1, 2020

Would it be possible to update this to make it even more clear, or add a suggestion that if you are getting issues this could be the cause? As this is no longer a very recent version of Node people are likely to have other versions installed. See issue #1035 for another example of someone running into this.

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

No branches or pull requests

3 participants