Hi Ton
Thanks again for your help on this one !.
I definitely have npm added to my path (see below), but dont see the customvis.cmd file available in the directory...
C:\Users\water\AppData\Roaming\npm>dir Volume in drive C has no label.
Volume Serial Number is 9CF7-E6A2
Directory of C:\Users\XXXX\AppData\Roaming\npm
29/10/2019 12:47 <DIR> .
29/10/2019 12:47 <DIR> ..
29/10/2019 12:48 0 cls
29/10/2019 12:48 0 dir
29/10/2019 12:48 0 lib
28/10/2019 15:14 <DIR> node_modules
29/10/2019 12:48 0 npm
29/10/2019 12:48 0 types
5 File(s) 0 bytes
3 Dir(s) 289,297,469,440 bytes free
C:\Users\xxxx\AppData\Roaming\npm>pathPATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\130\Tools\Binn\;C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files\Microsoft SQL Server\140\Tools\Binn\;C:\Program Files\Microsoft SQL Server\140\DTS\Binn\;C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\;C:\Program Files\IBM\SPSS\Modeler\18.2.1\ext\bin\spss.TMWBServer\bin;C:\Program Files\nodejs\;C:\Users\XXXX\AppData\Local\Microsoft\WindowsApps;
C:\Users\XXXX\AppData\Roaming\npm
------------------------------
Nick Waters
------------------------------
Original Message:
Sent: Tue October 29, 2019 08:40 AM
From: Ton Steijvers
Subject: 11.1.4 Custom Vis - cannot start
Hi Nick,
So far this looks good. If you look in 'C:\Users\XXXX\AppData\Roaming\npm' you should see a customvis.cmd file. This is the command that should be executed when you type 'customvis' anywhere on the command line.
Can you verify that 'C:\Users\XXXX\AppData\Roaming\npm' is in your search path? You can type path on the command line to see what is currently in your search path. If it isn't, you can use setx PATH "%PATH%;C:\Users\XXXX\AppData\Roaming\npm" to update your search path. You might need to restart the cmd process for the new path to take effect.
Regards,
Ton
------------------------------
Ton Steijvers
------------------------------
Original Message:
Sent: Tue October 29, 2019 08:14 AM
From: Nick Waters
Subject: 11.1.4 Custom Vis - cannot start
Hi Ton
Thanks for your speedy response !. Here is the output from npm bin -g
C:\Users\XXXX\AppData\Roaming\npm\node_modules\@businessanalytics\customvis-lib>npm bin -g
C:\Users\XXXX\AppData\Roaming\npm
Looking into the directory structure further I can see the following directories...
C:\Users\XXXX\AppData\Roaming\npm\node_modules\@businessanalytics\customvis-lib>dir
Directory of C:\Users\XXXX\AppData\Roaming\npm\node_modules\@businessanalytics\customvis-lib
28/10/2019 15:14 <DIR> .
28/10/2019 15:14 <DIR> ..
28/10/2019 15:14 <DIR> lib
28/10/2019 15:14 2,334 package.json
26/10/1985 08:15 1,955 readme.md
28/10/2019 15:14 <DIR> types
Regards
Nick
------------------------------
Nick Waters
Original Message:
Sent: Tue October 29, 2019 06:23 AM
From: Ton Steijvers
Subject: 11.1.4 Custom Vis - cannot start
Hi Nick,
It looks as if the npm bin folder is not in your search path. You can do the following:
1. execute 'npm bin -g' to find out where npm stores your global modules.
2. list the contents of the folder that you got in step 1. You should see 'customvis' in here.
3. add the folder from step 1 to your PATH. How to do this depends on your operating system.
Note that you might have to restart your cmd / terminal process to have the PATH setting take effect.
Regards,
Ton Steijvers
------------------------------
Ton Steijvers