lambtron / lambtron/medium-cli
A lot of errors
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 85
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Hi!
Thanks for the script. Unfortunately, I couldn't get it working. Below is the code.
Do you have any ideas on how to make it work?
Thanks,
Joni
C:\Users\joni>npm install -g medium-cli
npm WARN deprecated metalsmith-templates@0.7.0: This package was split into two simpler plugins: metalsmith-layouts and metalsmith-in-place
npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated lodash.createcallback@2.4.4: This package is discontinued. Use lodash.iteratee@^4.0.0.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
C:\Users\joni\AppData\Roaming\npm\medium -> C:\Users\joni\AppData\Roaming\npm\node_modules\medium-cli\bin\medium
C:\Users\joni\AppData\Roaming\npm
-- medium-cli@0.0.7
-- khaos@0.9.3
-- to-case@1.0.2
-- to-camel-case@0.2.1 (git+ssh://git@github.com/ianstormtaylor/to-camel-case.git#02759f7dcf1b3a9c05568183dc14c738d2a0e229)
C:\Users\joni>medium login
events.js:160
throw er; // Unhandled 'error' event
^
Error: spawn C:\Users\joni\AppData\Roaming\npm\node_modules\medium-cli\bin\medium-login ENOENT
at exports._errnoException (util.js:1022:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Windows installation and medium login command shown in the report. Inspect the installed bin/medium entry point and the referenced medium-login path to determine why Node reports ENOENT; done means the login command starts successfully after npm install -g medium-cli.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100