Hello team.

I'm llofyy and I'm creating this theme from the Ballerini community to Hyper.

https://github.com/llofyy/hyper-ballerini-theme

Automatic deployment with Now seems to be broken.
The 5 most recent pull requests seem to be blocked due to lacking Now authorization.

To make the personalized routes we use express we can change it to micro.js, it should not be so complicated to make this change 😸

See #157. Opening this issue per @pacocoursey’s comment:

Manual selection is a good idea, if you still feel strongly about adding it as a feature please open a new issue.

The now bot has failed my pull request due to lack of authorization.
How do I create a valid pull request?
Regarding pull request #118

Hi Team,

Shall we have Spacedust theme for hyperterm. it's really amazing theme and our lovely terminal store missing it.

Here is the reference link and i hope soon this will show up in hyperterm theme store.

https://github.com/hallski/spacedust-theme

I'm sorry, but the current website doesn't look good and it's not easy to get you started.

I thought micro was the zeit choice for http servers.
Why is this project using express?

The hyper-shellect plugin on the website has been deprecated and must be replaced by hyper-shellect2

It appears as though the service from which the site was getting package metadata (npms.io) is no longer being maintained.

I suggest making the calls against registry.npmjs.org, though this will require reworking some of the fields that were expected to be coming out of the "metadata" object.

Calls to registry.npmjs.org can be made as follows https://registry.npmjs.org/${name}/latest to retrieve the latest data on a package.

From vercel/hyper#3153:

It would be nice to see the latest official version of hyper on the website near the download buttons.

Maybe it would be nice to also note what release channel is on which version.

As already mentioned in the other issue, the version number (latest/prerelease) can be obtained via the github api or if there is a build setup - during buildtime you can pass env vars maybe

response = await fetch('https://api.github.com/repos/zeit/hyper/releases')
releases = await response.json()
latestStable = releases.find(release => !release.prerelease)
console.log(latestStable.tag_name)

Hey!

The site could use a little bit of elbow grease, the audit scores are quite low for a fully static website. I'll try my best clean up the repo, use the latest Next.js features, etc. I'll note any changes that are not part of the 1:1 rewrite but made sense for one reason or antoher.

See current progress in #172.

Let me know if you want anything else fixed, also I would love to receive some feedback.

I know these are simple questions, but I have been genuinely curious about using this terminal over others that are out there, and I have not been able to find a clear reason why I or we should even use it.

Upon further inspection, I do see that you state These shell commands are defined internally., meaning that it is completely based on the actual command lines running on every operating system. What difference would it make if I had Hyper, then?

Maybe it is on my side, a common person, in addition to being a mere novice to coding and JavaScript. Please, let me know if I have any misconceptions! Though, it would be helpful, anyhow, if you could have your documentation make the purpose (more) apparent.

The highlighting when searching the store on hyper.is is broken. Try searching, then remove the search query. It still highlights the first character.

At https://hyper.is/#config-location, it reads:

macOS: ~/Library/Application Support/Hyper/.hyper.js
Windows: $Env:AppData/Hyper/.hyper.js
Linux: ~/.config/Hyper/.hyper.js

Note: config at ~/.hyper.js still supported, but will be ignored, if config in application directory present. Otherwise it will be moved to the application directory at first run.

Observations:

1. On a fresh install of Hyper on macOS 10.15:

   • ~/.hyper.js is created
   • ~/Library/Application Support/Hyper/.hyper.js is not created

2. Changes saved to ~/.hyper.js are reflected in the app

3. If I copy and paste customized config contents into ~/Library/Application Support/Hyper/.hyper.js and then delete ~/.hyper.js, Hyper does not seem to recognize the customized config.

It seems that the documentation does not represent the current behavior of Hyper.

I have only recently begun to explore Hyper, so I would like to understand this better: is the documentation outdated or is it new information that is planned for a future release, but is not yet relevant?

Either way, the docs should probably be updated to reflect the current app behavior.

All ZEIT projects have a README file, I find it strange that this project does not have one 🤔

example from localhost.

what do you think about this matter?

Love the store and how it looks! Thank you all a lot for your work!
I am using this theme lately and I was thinking if it would be a good fit for the store;

• Link: https://github.com/klauscfhq/hyperocean
• Screenshot::
  
  If you think it is interesting enough I can create a pull request! Thank you again for your time!

Platform detection is not working correctly on the website:

This causes incorrect info to be displayed regarding paths:

If manual selection of platform were possible, this could be corrected, but I don't see that there is a way to manually select my platform. Perhaps this can be added.

Environment in screenshots:
OS: macOS 10.15
Browser: Chrome 77.0.3865.120 (Incognito—No extensions)

doesn't quite match the blog post:

on live website 'hyper.is' when click the logo (left top) got 'An unexpected error has occurred' in Firefox browser.

<a class="jsx-2327597585 logo" href="/">

I get this error after running npm install:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.2.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.13.1 || ^17.0.0" from @mdx-js/[email protected]
npm ERR! node_modules/@mdx-js/react
npm ERR!   @mdx-js/react@"^1.6.4" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

The React version of the module @mdx-js/react is conflicting.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

All of the theme/plugin links on /themes, /themes?newest, /plugins, and /plugins?newest had surprising behavior:

• ctrl-click-ing them did not open a new tab, instead navigating in the current tab (this can be a jarring experience when I'm attempting to pick three or four links out of a list and the first one takes the list away from me.)
• Right-clicking on them gives you a standard page menu instead of a link menu with options like "Copy link address" or "Open in new tab"
• None of the links showed up in the tab sequence, so I couldn't tab through the list of plugins.

Tested in both Chrome 75 and Firefox 67 on Fedora Linux.

I'm opening up this issue to keep track of a few plugins/themes that have dead preview image links

• hyper-arc-dark-controls
• hyper-dark-scrollbar
• hyper-shellect

This is a topic a little more related to the design, Currently all the themes that are in hyper store are following this line of design. It should be mandatory to follow this design line only in themes.

@evilrabbit 🐰 I would like to know your opinion about this

i have to tell emacs that this is a vt100, rather than xterm, since insert-character isn't implemented. intended?

Links have almost the same styling as surrounding body text