Extensions API about hyper

[rauchg]

As far as how someone register their extensions, I was thinking about having $HOME/hyperterm.json.
It would look as follows:

[
  "@hyperterm/preserve-pwd",
  "hypersolar"
]

This has a few purposes:

• Sharability. "👨: Why does your hyperterm look so cool!? "👩: Here, have my hyperterm.json".

• Configurability and extensibility in one. If you want to remove functionality, simply remove a core plugin. Plugins admit optional parameters:

  ["hypersolar", { "useWeatherAPI": true, "zipCode": 94123 }]

• Declarative installation. Kind of like the amazing .vimrc based extensions solutions (I use NeoBundle). When you make changes to the file, that triggers the installation or removal of the NPM modules.

The NPM modules will be installed inside ~/.hyperterm-modules

[rauchg]

As far as the API, I'm going to experiment with the following: plugins simply expose a function that is invoked with the main <HyperTerm> component to decorate.

This would give plugins complete control over the customizability of the terminal. They could register componentDidMount, add stuff to render, etc.

[chabou]

Outdated