search

samyk / easel-driver

Easel driver for Linux, Mac, Windows, ARM, Raspberry Pi, Intel, FTDI, CH340, CH341, CP210x, FTDI clones, local, and remote access to GRBL-based CNC controllers
95 stars 24 forks source link

can't find socket.io? #10

Closed emsilva closed 4 years ago

emsilva commented 4 years ago

sorry, this must be very stupid but I know nothing about node.

`pi@cnc-control:~/easel-driver $ cat screenlog.0 internal/modules/cjs/loader.js:968 throw err; ^

Error: Cannot find module 'socket.io' Require stack:

any idea of what could be going on?

samyk commented 4 years ago

Can you paste the full output from running the installation? You can re-run it.

emsilva commented 4 years ago

Sure thing. Thank you.

`pi@cnc-control:~ $ curl https://raw.githubusercontent.com/samyk/easel-driver/master/easel-driver.sh | sh -x % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3287 100 3287 0 0 38670 0 --:--:-- --:--:-- --:--:-- 38670

7-Zip [32] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,32 bits,4 CPUs LE)

Scanning the drive for archives: 1 file, 23567283 bytes (23 MiB)

Extracting archive: EaselDriver.pkg

WARNINGS: There are data after the end of archive

-- Path = EaselDriver.pkg Type = Xar WARNINGS: There are data after the end of archive Physical Size = 23565515 Tail Size = 1768 SubType = pkg Headers Size = 4940

Everything is Ok

Archives with Warnings: 1

Warnings: 1 Folders: 3 Files: 12 Size: 24998913 Compressed: 23567283

=> nvm source string already in /home/pi/.bashrc => bash_completion source string already in /home/pi/.bashrc => You currently have modules installed globally with npm. These will no => longer be linked to the active version of Node when you install a new node => with nvm; and they may (depending on how you construct your $PATH) => override the binaries of modules installed with nvm:

/home/pi/.config/nvm/versions/node/v12.18.4/lib └── socket.io@2.3.0 => If you wish to uninstall them at a later point (or re-install them under your => nvm Nodes), you can remove them from the system Node as follows:

 $ nvm use system
 $ npm uninstall -g a_module

=> Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="$HOME/.config/nvm" [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm [ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion

samyk commented 4 years ago

Is it running if you run screen -r?

What if you manually run: cd ~/easel-driver && node iris.js # does this work?

emsilva commented 4 years ago

No luck. Must be something really stupid from my side.

Imagem PNG
samyk commented 4 years ago

Nothing stupid! Can I try ssh'ing into the system to see why it's not getting installed? We can set up a reverse ssh tunnel to my server so you don't have to open anything up. You can email me privately and I can share the ssh + password: s [at] samy.pl

emsilva commented 4 years ago

Sent! Talk to you soon

samyk commented 4 years ago

This was due to nvm being installed in a different dir (~/.config/nvm instead of ~/.nvm), the script now checks for $NVM_DIR and uses that if it exists, otherwise tests for those two dirs and uses whichever exists. Fixed in [95f0e78e288e63c075d278158cfe042170985faa].

Thanks!

emsilva commented 4 years ago

Awesome. Appreciate your support!