search

alleyway / add-tradingview-alerts-tool

Automated entry of TradingView alerts for bot trading tools such as 3Commas, Alertatron, CryptoHopper, etc.
MIT License
623 stars 140 forks source link

Installation of new version error #121

Closed ocmich74 closed 2 years ago

ocmich74 commented 2 years ago

image

How do I resolve this?

m4ybee commented 2 years ago

This worked for me:

2) You can reinstall/update this project by running the following:

npx @alleyway/create-tradingview-alerts-home

tip. do it inside the existing tradingview-alerts-home directory.

ocmich74 commented 2 years ago

I tried that, didn't work. I'm more concerned with the empty folder that won't delete. I have 3 of them now that won't delete from my computer.

mlake commented 2 years ago

hi there - what versions of windows/node/npm are you using?

ocmich74 commented 2 years ago

I am on windows 10.. Not sure node/npm because i deleted them a week ago and haven't added them back.

newquestions commented 2 years ago

The installation is broken. I am using the latest version of Windows 10, and Node and NPM.

Above image explicitly shows the problem. The installation may have worked in the past ... but not any longer.

mlake commented 2 years ago

hi @newquestions

I don't have a windows machine, but I have tested installation on a Win10 virtual machine with no problems.

The more specific information you can give me, the better I could try to reproduce and fix the problem (as well as research how you might be able to remove those folders...)

when you say "latest version of node"...do you mean version 16 or 18?

will work on this today...

mlake commented 2 years ago

also...

were you using windows "Command Prompt"? or was it "Powershell"?

screencap
mlake commented 2 years ago

Should be solved. but will keep this issue open for now

123

ocmich74 commented 2 years ago

My issues are solved. I was able to remove all the empty folders and I was able to reinstall the tool with zero issues. Thank you for fixing this!

newquestions commented 2 years ago

Can confirm the new update has worked correctly. Thank you Michael.

One thing you may want to include in the docs is this idea ...

Seems Powershell has default protection in place for unsigned packages downloaded via the internet.

As a result, I had to run this command, which offers a temporary bypass on the unsigned package:

powershell -executionpolicy ByPass -File .\atat.ps1 fetch-symbols binance -q usdt

Thanks again!

mlake commented 2 years ago

interesting . hadn't come across that before. will add to troubleshooting