bahmutov / bahmutov/next-update

Combination on --available and --changed-log fails

Open
#115 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
557
Forks
16
PR merge metrics
No merged PRs in 30d

Description

I would have expected
`next-update --available --changed-log`
to work, but it fails with the message
```
_.pluck(toCheck, 'name'),
^
TypeError: _.pluck is not a function
at Object.available (/home/dev/.../node_modules/next-update/src/next-update.js:29:11)
at Object. (/home//dev/.../node_modules/next-update/bin/next-update.js:29:6)
at Module._compile (module.js:624:30)
at Object.Module._extensions..js (module.js:635:10)
at Module.load (module.js:545:32)
at tryModuleLoad (module.js:508:12)
at Function.Module._load (module.js:500:3)
at Function.Module.runMain (module.js:665:10)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
```

Any chance to make this available?

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce `next-update --available --changed-log`, then inspect `src/next-update.js` around the `available` entry point and `bin/next-update.js` around command dispatch, as named in the stack trace. Confirm the combined command no longer throws and produces the expected availability and changed-log output.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.