vercel / vercel/hyper

auto downgrade?

Open
#7,504 1 comment 2 reactions 0 assignees View on GitHub

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
  • I have searched the issues of this repo and believe that this is not a duplicate
  • OS version and name: MacOS 14.0 Sonoma
  • Hyper.app version: 3.4.1
  • Link of a Gist with the contents of your hyper.json: https://gist.github.com/ldeveber/0eaa35e0b1fe22b8884dc0b310c0be40
  • Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
    (re)loading renderer plugins
    bundle.js:1 Plugin hyperpower (1.1.1) loaded.
    bundle.js:1 Plugin hyper-horizon-theme (1.1.01) loaded.
    bundle.js:1 Plugin hyper-tabs-enhanced (0.4.2) loaded.
    bundle.js:1 Plugin hyper-manager (1.0.6) loaded.
    ​ total init time 269
    DevTools failed to load source map: Could not parse content for file:///Applications/Hyper.app/Contents/Resources/app.asar/utility.js.map: Unexpected end of JSON input
    
  • The issue is reproducible in vanilla Hyper.app:

Issue

Not sure why its trying to downgrade from 3.4.1?
Screenshot 2023-09-29 at 10 31 39 AM

Screenshot 2023-09-29 at 10 30 40 AM

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the supplied hyper.json, the Hyper.app version details, and the DevTools output, then reproduce the downgrade prompt on macOS 14.0 with Hyper 3.4.1. Done means identifying the trigger for the prompt and confirming that the app no longer proposes an unintended downgrade.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.