Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

port is not defined #18

Closed
otbe opened this issue Nov 12, 2016 · 3 comments
Closed

port is not defined #18

otbe opened this issue Nov 12, 2016 · 3 comments
Assignees
Milestone

Comments

@otbe
Copy link

otbe commented Nov 12, 2016

Hi,

I installed the latest version of nodemcu-tool, but I get ReferenceError: port is not defined even with --port.

$ nodemcu-tool devices --port /dev/tty.wchusbserial1410
/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/lib/NodeMCU-Tool.js:408
    var connector = new _nodeMcuConnector(port, baud);

ReferenceError: port is not defined
    at Object.Tool.devices (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/lib/NodeMCU-Tool.js:408:43)
    at Command.<anonymous> (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/bin/nodemcu-tool.js:373:22)
    at Command.listener (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/node_modules/commander/index.js:301:8)
    at emitTwo (events.js:106:13)
    at Command.emit (events.js:191:7)
    at Command.parseArgs (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/node_modules/commander/index.js:615:12)
    at Command.parse (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/node_modules/commander/index.js:458:21)
    at Object.<anonymous> (/Users/boo/.nvm/versions/node/v6.9.1/lib/node_modules/nodemcu-tool/bin/nodemcu-tool.js:406:6)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)

nodemcu-tool version is 2.0.0

Whats wrong with my attempt? :)

Thanks!

@AndiDittrich
Copy link
Owner

i will check this today

@AndiDittrich
Copy link
Owner

Thanks Benjamin!

it was caused by a refactoring issue fixed in v2.0.1

@AndiDittrich AndiDittrich added this to the v2.0.1 milestone Nov 12, 2016
@AndiDittrich AndiDittrich self-assigned this Nov 12, 2016
@otbe
Copy link
Author

otbe commented Nov 12, 2016

Works great. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants