not support shelljs package
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9.8k
- Forks
- 326
- PR merge metrics
- No merged PRs in 30d
Description
(node:110708) UnhandledPromiseRejectionWarning: TypeError: shelljs_1.default.exec is not a function
at exeList.forEach.item (evalmachine.:7230:42)
at Array.forEach ()
at addCommit (evalmachine.:7229:13)
at inquirer_1.default.prompt.then (evalmachine.:7333:13)
at process._tickCallback (internal/process/next_tick.js:68:7)
(node:110708) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:110708) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
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 shelljs failure in ncc and inspect the generated code around evalmachine lines 7229-7333, where addCommit invokes shelljs_1.default.exec. Done means a project using shelljs runs without the reported TypeError or unhandled promise rejection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100