-
Notifications
You must be signed in to change notification settings - Fork 9
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
What is the recommended nodejs version? #6
Comments
I wanted to report that I updated to the latest available firmware at the time of this writing using a Windows 10 guest through VirtualBox. Here are my Roccat software and firmware versions:
Additional information:
Even having the keyboard at the latest firmware still yields the same error provided from my previous comment. |
Hi Erockce |
Come back later... now its two years later... you probably dont use it anymore, but anyways: Published a new version, it should run now with the newest node version. |
Hi...I'm really new to
nodejs
but have an IT and Software Development background.I just purchased the Roccat Vulcan 120 and trying some of the open-source projects that work with it since my primary platform is Linux.
My question is: What version of
nodejs
should be used for this project and your other programs?I am currently using NodeJS 12 LTS, but I'm having trouble just running the example code on the main page after I made a copy of the
de-de
layout to start the creation ofen-us
. After moving the file into thesrc
directory then it failed findinggrid.js
. So I reverted back tode-de
just so I could get going.I get further but am receiving the a
UnhandledPromiseRejectionWarning
when I run the file:So then I added the recommended "
--unhandled-rejections=strict
". And get a bit further and with a different error. The lights do get changed to BRIGHT yellow. However then something strange happens where the FN+[F1-F4] doesn't work and the brightness control does not let me change the brightness back up from all the way off (and I did press theFX
button first).Unplugging and then plugging back in reset the keyboard and it returned back to the profile on FN-F3.
This keyboard is brand new from my local electronics store and I have not used the Swarm software (I don't know yet if it will work from a Windows 10 virtual machine) yet.
Sorry this changed from a question to a possible bug.
This is my first RGB and mechanical keyboard. I am so very grateful to see people like you working on a open-source user-space applications to interact with these RGB keyboards!
The text was updated successfully, but these errors were encountered: