expose xterm.js' `loadAddon` to plugins
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
Feature request:
xterm.js is extensible via addons. Hyper currently loads a static set of addons (https://github.com/zeit/hyper/blob/bad51f9c15a9f094588a3c3e36bea2b5151d4606/lib/components/term.tsx#L154-L158). It would be useful to allow plugins to enable additional addons.
One of the main motivators behind this would be to allow for custom ILinkProvider to enhance user interaction with text objects. Some examples of link providers beyond the static WebLinksAddon could be matching emails or user provided regexes as requested in https://github.com/xtermjs/xterm.js/issues/2893.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in lib/components/term.tsx around the static addon loading at lines 154-158, then trace how plugins are exposed to the terminal. Done means plugins can enable additional xterm.js addons, including custom link providers beyond WebLinksAddon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100