As a node newbie, I don't understand what to do after install about cli-tweet

[raed667]

@wykydtronik thank you for your interest in this project.

I realize that the documentation could have been better. I haven't used Windows for a long time, but here is some setup that should work:

• Open your CMD there and type npm install cli-tweet -g

• When it finishes you should close your CMD and open a new one

• Try typing tweet config to configure the tool to use your credentials, it will give you a link that will get you a PIN number to input.

• If you can't find the command 'tweet' after installing, you should type npm root and add that to your PATH.

Hope this helps

[raed667]

@wykydtronik : Thank you for the feedback, I think that I can see what the problem is.

I don't own a machine running Windows, but I will try to make this work as soon as possible. Watch the repo for updates.

[raed667]

@wykydtronik can you try using the code in this branch and telling me if it works on your windows ?

https://github.com/RaedsLab/cli-tweet/tree/windows-support

basic usage should be :

node main.js config

this should create a '.tweet.json' file under your home directory.

If this works I'll merge it and make it available from NPM.

[wykydtronik]

Hi @RaedsLab !

I got it to work with one minor hick up. When I attempted to use tweet config, I got this error below.

fs.js:640
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: EPERM: operation not permitted, open 'C:\Program Files\Git\.tweet.json'
    at Error (native)
    at Object.fs.openSync (fs.js:640:18)
    at Object.fs.writeFileSync (fs.js:1333:33)
    at C:\Users\[USERNAME-PLACEHOLDER]\AppData\Roaming\npm\node_modules\cli-tweet\main.js:33:16
    at C:\Users\[USERNAME-PLACEHOLDER]\AppData\Roaming\npm\node_modules\cli-tweet\node_modules\oauth\lib\oauth.js:472:12
    at passBackControl (C:\Users\[USERNAME-PLACEHOLDER]\AppData\Roaming\npm\node_modules\cli-tweet\node_modules\oauth\lib\oauth.js:390:11)
    at IncomingMessage.<anonymous> (C:\Users\[USERNAME-PLACEHOLDER]\AppData\Roaming\npm\node_modules\cli-tweet\node_modules\oauth\lib\oauth.js:409:9)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)

The solution to this was to run Powershell/CMD in Administrator mode. Once I did that, it gave allowed permissions to write the .tweet.json file in that location. I really appreciate your response! I hope this can help anyone that finds your project. :)

[wykydtronik]

@RaedsLab The installation works without Administrative mode!

As a precaution, I uninstalled and reinstalled it twice on my desktop PC. Also, I tried it on my Windows 10 laptop. I am able to tweet from the command line on both of my Windows 10 machines.

Edit: I was curious to test this on a fresh Win10 installation. I fired up a VM and installed Windows 10 Pro. I installed Node.js and was able to configure cli-tweet within seconds. Looks like it's working great. I didn't have to mess with the PATH but it could be optional work around like my scenario before. I noticed node.js offers including it in the PATH. I am not sure how recent that was but in my case I had to include it on both my laptop and desktop. The VM had it included at installation.

npm install cli-tweet -g
tweet config
echo "Hello Universe" | tweet

[wykydtronik]

@RaedsLab windows-support branch also works on macOS

[raed667]

@wykydtronik great news! thank you !

I'll merge with master branch and share it on NPM tonight.