RFC: Hyper 3 Migration

Problem

We changed the location of the config file in Hyper 3 (Windows) without proper a proper migration path causing disruption to users updating from the stable branch.

Workaround

If you’re experiencing this issue, you can copy your .hyper.js from C:\Users\<username>\ to: C:\Users\<username>\AppData\Roaming\Hyper and restart hyper.

If you keep having issues with Hyper 3 you can also temporarily downgrade to Hyper 2 but please report any issues so we can fix them in a timely manner

Fix

We have a couple of potential fixes:

1. Revert the location to the previous one
2. Detect if there’s a file in the old location and copy/move it to the new location, backing up any existing ones in the new location (probably a fresh config augenerated by Hyper 3)

I think (2) is the way to go but would like to hear opinions from the community (cc: @Stanzilla, @mazyi, marekkaczkowski)

Improving testing

Moving forward we would like to prevent this from happening again. The way to do this is by improving our testing infrastructure. We’re accepting proposal to and collaboration on this front. If you’re interested feel free to let me know and we can coordinate

[Stanzilla]

I vote 2,

if there already is a file in the new location, which is only the case if the user already upgraded, overwrite it but keep a backup and tell the user what happened.

[MaxySpark]

After updating to v3 when I use clear command it doesn’t work properly. I need to scroll up and down to apply the clear effect. In v2 I didn’t get this issue.