2
2
mirror of https://github.com/Llewellynvdm/nativefier.git synced 2024-11-16 10:05:09 +00:00
nativefier/.github/ISSUE_TEMPLATE/bug_report.md

40 lines
1.3 KiB
Markdown
Raw Normal View History

---
name: Bug report
about: Create a report to help us improve
labels: bug
---
<!-- Help us help you, please take the time to fill this information 🙂.
An incomprehensible bug report is a useless bug report.
Incomprehensible / incomplete bug reports will be closed. -->
2020-03-10 13:19:02 +00:00
**Bug description**
A clear and concise description of what the bug is.
2020-03-19 16:30:08 +00:00
- [ ] I looked at `nativefier --help` and https://github.com/jiahaog/nativefier/blob/master/docs/api.md
2020-03-10 13:12:46 +00:00
- [ ] I searched existing open & closed issues. Yes, my bug is new.
- [ ] I'm using the latest version available at https://github.com/jiahaog/nativefier/releases
2020-03-10 13:12:46 +00:00
**Steps to reproduce**
2020-03-10 13:17:05 +00:00
Give your ***full*** nativefier command, with the ***`--verbose` flag***, on a ***public*** site:
1. Run `nativefier --verbose ...`
2. ...
**Expected behavior**
What you expected to happen.
**Actual behavior**
What happened instead.
2020-03-19 16:30:08 +00:00
**Debug info**
Verbose logs (command-line and/or in app DevTools console), error message, screenshots
**Context**
2020-03-19 16:30:08 +00:00
- Nativefier: (for example: 8.0.4)
- Node.js: (for example: 13.11.0)
- Npm: (for example: 6.14.7)
- OS: (for example: Windows 10 build 1809)
2020-03-19 16:30:08 +00:00
- Is it a regression? If yes, what's the last working / first broken version?
- Additional context: (for example: "I'm behind a proxy, with config. X and protocol Y")