vercel/hyper

User-unfriendly error when adding a new plugin

Open

Aperta il 21 set 2017

Vedi su GitHub
 (0 commenti) (0 reazioni) (0 assegnatari)TypeScript (44.582 star) (3558 fork)batch import
help wanted🎨 Type: Enhancement

Descrizione

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:

screen shot 2017-09-21 at 17 46 59

… 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! (=

Guida contributor

Tech stack
typescriptreactnodejs
Dominio
desktopdeveloper experience
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
2
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
under 1 hour
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
mostly clear
Prerequisiti
basic understanding of Electronknowledge of Hyper plugin system
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
80
Direzione di ricerca
Examine the plugin loading code in Hyper, specifically the initialization sequence when the app starts. Compare with the hot reload path that shows a friendly notification. Look for where error messages are generated (likely in the plugin loader module, e.g., 'plugin loader.ts' or similar). The fix should ensure that if a plugin is not yet installed on initial launch, it either waits or provides a clear message instead of an unhelpful error. Consider adding a timeout or retry mechanism with user feedback.