jprichardson / jprichardson/node-suppose
Doesn't work on windows
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 255
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
since https://github.com/jprichardson/node-suppose/commit/982264c33d3a00a4cb6aa3bf4dd2200f235412c1
Error: File not found:
at new WindowsPtyAgent (node_modules\node-pty\lib\windowsPtyAgent.js:25:24)
at new WindowsTerminal (node_modules\node-pty\lib\windowsTerminal.js:45:23)
at spawn (node_modules\node-pty\lib\index.js:27:12)
at SupposeProcess.end (node_modules\suppose\lib\suppose-process.js:74:11)
at Promise (test.js:60:4)
at Promise (<anonymous>)
at interaction (test.js:42:9)
at dotenvPrompt.then (test.js:82:15)
at <anonymous>
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 comparing commit 982264c33d3a00a4cb6aa3bf4dd2200f235412c with its parent, then trace the Windows failure through node_modules\node-pty\lib\windowsPtyAgent.js, windowsTerminal.js, and suppose-process.js. Use test.js, especially the interaction around lines 42, 60, and 82, to reproduce the problem. Done means the Windows execution path no longer reports this file-not-found error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100