why windows?
- Dominant language
- C++
- Stars
- 182
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
npm ERR! Windows_NT 6.2.9200
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g
npm ERR! node v4.5.0
npm ERR! npm v2.15.9
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported
npm ERR! notsup Not compatible with your operating system or architecture: vock@0.5.0
npm ERR! notsup Valid OS: darwin,linux
npm ERR! notsup Valid Arch: any
npm ERR! notsup Actual OS: win32
npm ERR! notsup Actual Arch: x64
npm ERR! Please include the following file with any support request:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking the npm package metadata for vock@0.5.0, which reports support for darwin and linux but not Windows. Determine whether Windows is intended to be supported; done means the platform restriction or the expected lack of Windows support is clearly explained.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100