-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Desktop: Dev branch not working with node 16 #10234
Comments
|
Also, I saw on the internet( 1, 2, 3 ) a lot of people having similar errors (including me) like these:
Nothing from the internet worked. It didn't allow me to run the commands for clearing the cache because of this error . I ran everything as an administrator, I didn't have anything Node-related opened, I tried multiple versions of Node using nvm, etc.. After I ran
So, I made sure to have a fresh start before cloning and working on this project. I think there can be some issues with multiple versions of npm/yarn (since I also had installed yarn through npm before). Maybe this helps someone in the future. |
|
Yes I think we need more than Node 16 by now, and the doc and other places should be updated. I use Node v19.6.1. Could you check if it's working with that version? |
|
I followed the same steps for clearing everything Node-related (I forgot to mention but in Program Files the folder "nodejs" should also be deleted since I had problems with it) I installed Node 19.9.0 and after running |
Operating system
Windows
Joplin version
last version from dev branch
Desktop version info
No response
Current behaviour
Steps to reproduce:
yarn install, this was the output:The last line that starts with root@workspace is problematic. I also attached the logs, and there you can find the following errors:
Expected behaviour
Regarding the first error: I searched on the Node website, Readline section, the correct syntax:
Fix:
const readline = require('readline/promises');toconst readline = require('readline');After this change, I was able to start the application. The second error was because of @joplin/lib, but I do not know the solution.
Logs
error node 16.txt
The text was updated successfully, but these errors were encountered: