Not able to run the nodemcu-tool.js

Question

Not able to run the nodemcu-tool.js

Ankitr19 opened this issue 8 years ago · 6 comments

Please help!!

Answer 1 · 2017-07-25T06:48:59.000Z

Hi Ankit,

this seems to be an issue with the serialport package - not NodeMCU-Tool.

Please take a look onto their FAQs - in most cases such errors a caused by a missconfigured environment.
did you try to install the tool in the local folder instead of global scope ?

br, Andi

Answer 2 · 2017-07-25T06:59:28.000Z

Sir, now when I am trying to install it locally, i.e. just by cloning the git repo and running the nodemcu-tool.js it is giving another error.

…

On 7/25/17, Andi Dittrich ***@***.***> wrote: Hi Ankit, this seems to be an issue with the [serialport](https://github.com/EmergingTechnologyAdvisors/node-serialport) package - not NodeMCU-Tool. Please take a look onto their FAQs - in most cases such errors a caused by a missconfigured environment. did you try to install the tool in the local folder instead of global scope ? br, Andi -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #43 (comment)

-- Ankit Raj Electronics and Communication Engineering NIT Agartala 8414846511

Answer 3 · 2017-07-25T07:02:58.000Z

in this case you have to run npm install to fetch the dependencies...

normally a simple npm install nodemcu-tool should do the job

Answer 4 · 2017-07-25T07:10:52.000Z

Sir a little query, when I run npm isntall nodemcu-tool where it gets install. I mean where I can find the. js file to execute it? Ankit Raj, B. Tech, Electronics and Communication Engineering NIT Agartala 8414846511

…

On 25-Jul-2017 12:33 pm, "Andi Dittrich" ***@***.***> wrote: in this case you have to run npm install to fetch the dependencies... normally a simple npm install nodemcu-tool should do the job — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#43 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXfyuYiJz7J-ql1XoWWmvhxR1Jb8jl8-ks5sRZMjgaJpZM4OiDNR> .

Answer 5 · 2017-07-25T07:15:29.000Z

Please read the readme file first ;)

in case you've cloned the github repo
the "executable" file is located in ./bin/nodemcu-tool.js
https://github.com/AndiDittrich/NodeMCU-Tool#as-archive-from-github

in case of local npm installation
the "executable" file is located in ./node_modules/nodemcu-tool/bin/nodemcu-tool.js
https://github.com/AndiDittrich/NodeMCU-Tool#localproject-related-installation

Answer 6 · 2017-07-25T07:31:04.000Z

Yes, Sir, it worked. :)

…

On 7/25/17, Andi Dittrich ***@***.***> wrote: Please read the readme file first ;) **in case you've cloned the github repo** the "executable" file is located in `./bin/nodemcu-tool.js` https://github.com/AndiDittrich/NodeMCU-Tool#as-archive-from-github **in case of local npm installation** the "executable" file is located in `./node_modules/nodemcu-tool/bin/nodemcu-tool.js` https://github.com/AndiDittrich/NodeMCU-Tool#localproject-related-installation -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #43 (comment)

-- Ankit Raj Electronics and Communication Engineering NIT Agartala 8414846511