User-unfriendly error when adding a new plugin
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
-
I am on the latest Hyper.app version (specifically,
-
I have searched the issues of this repo and believe that this is not a duplicate
-
OS version and name: macOS High Sierra 10.13 Beta (17A362a)
-
Hyper.app version: Hyper.app 2.0.2
-
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/ELLIOTTCABLE/6e13466d98f891f5d48afb7bd09c23e2
-
The issue is reproducible in vanilla Hyper.app: N/A
Issue
When installing a plugin the ‘cool’ way (modifying ~/.hyper.js while the terminal is running, adding a line, hitting save), the user-experience is actually pretty great — no strange errors, then suddenly a notification that the user can reload to see the changes. Cool!
However, if a more traditional method is employed — quitting the application before modifying its configuration — the experience is pretty unintuitive. If I quit, then add an entry to ~/.hyper.js, and then launch Hyper, I see this:

… followed by no further retraction or indication that, oh, hey, it just hadn't installed yet, everything is kosher now.
The “load plugins on initial launch” process needs to be modified to be as user-friendly if a package is not-yet-installed as the hot-reloading process! (=
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 tracing Hyper.app's initial-launch plugin loading and compare it with the hot-reloading behavior described for changes to ~/.hyper.js. The change is done when a not-yet-installed plugin produces the same clear, user-friendly status or notification during initial launch, without leaving the user with a misleading error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100