vercel / vercel/hyper

[Notification] Plugin error!: Plugin does not expose any Hyper extension API methods

Open
#3,144 3 comments 0 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 10.14
  • Hyper.app version: canary branch

Issue

Hello, I'm trying to create a plugin for Hyper. I'm exporting mapHyperDispatch in the module (as stated on the website). Launching with yarn run app, I get [Notification] Plugin error!: Plugin "xx" does not expose any Hyper extension API methods

I'm supposed to use mapHyperTermDispatch although it's disabled
https://github.com/zeit/hyper/blob/bc6101e98f6bb57239aa4184afa02ca223f9dacd/app/plugins/extensions.js#L34-L36

https://github.com/zeit/hyper/blob/bc6101e98f6bb57239aa4184afa02ca223f9dacd/lib/utils/plugins.js#L173-L177

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

Read app/plugins/extensions.js lines 34-36 and lib/utils/plugins.js lines 173-177, then reproduce the error with yarn run app using the reported mapHyperDispatch export. Done means the plugin API accepted by the canary branch is consistent with the documented export and no longer produces the reported notification.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
desktop, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.