How to use on Windows 64bit
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- desktop
Research direction
Reproduce the launch flow using github-reader-win64.zip from release 1.3.2: unzip it and run win64/github-reader.exe on Windows 64-bit. Inspect the resulting nw.js window and determine whether the application launches successfully; done means the GitHub client opens instead of showing only the nw.js window.
Written by the indexing model from the issue text.
Description
What I tried
- Downloaded https://github.com/azu/github-reader/releases/download/1.3.2/github-reader-win64.zip
- unzipped it
- Double-clicked win64/github-reader.exe
What happened
Only displayed a window titled "nw.js".
Is this the right way to launch on Windows?
- Dominant language
- JavaScript
- Stars
- 134
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
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.
More from azu/github-reader
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
azu/github-reader#7 ·
-
confuse message Open
Difficulty 3/5 1-2 days Newbie friendliness 20/100
azu/github-reader#2 ·
All issues in azu/github-reader
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
palladius/rails8-app-on-gcp#145 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
dotenvx/dotenv-vscode#139 ·
-
test-change-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
web-platform-tests/interop#1455 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100