Note: on the main process, plugins are registered as soon as possible (we fire onLoad). Otherwise they will be moved to the application directory at first run. Note: plugins at ~/.hyper_plugins still supported, but will be ignored, if plugins in application directory present. ~/Library/Application Support/Hyper/.hyper_plugins Invoking on* methods on the existing instances and re-rendering components with the fresh decorations in place.Pruning the require.cache in both electron and the renderer process.
#027658 hyperterm update
When the user clicks Plugins > Update all now.When changes are made to the configuration file ( plugins or localPlugins).hyper_plugins/local and then specify it under the localPlugins array in. When developing, you can add your plugin to. In the future we might do this automatically.
#027658 hyperterm windows
Plugins affecting the `BrowserWindow` will the effect on new windows after hot-reload. Please strive to make plugins that don't require a complete restart of the application to work. The user can hot-load and hot-reload plugins by pressing Command + R (refresh). Must return a Higher Order Component.Ī collection of useful module references for building components. Invoked with the React Componentto decorate. Must return an extended object of the map passed. The existing map of properties that will be passed to the component.Ī custom mapper for the dispatch properties. Note that for children components to get these properties, you have to pass them down using the corresponding methods (like getTermProps). uidĪ custom mapper for the state properties that container components receive. The existing properties that will be passed to the component. Subsequently we invoke the thunkmiddleware, which means your middleware can next thunks.Ī custom reducer for the ui, sessions or termgroups state shape. Invoked when a plugin is first loaded or subsequently reloaded in each window.Ī custom Redux middleware that can intercept any action. If a plugin reloads, it's called again and the menu is refreshed.Īllows you to decorate Electron's BrowserWindow options when a new window is created.
Invoked with the Electron's Menu template. Allows you to decorate the user's environment by returning a modified environment object. Useful for themeing or custom parameters for your plugin.
Allows you to decorate the user's configuration. Invoked when a plugin is removed by the user. If a plugin reloads, it's invoked again with the existing windows. If a plugin reloads, it's invoked again with the existing app. Your module has to expose at least one of these methods: You can find additional details about plugin development in the Hyper repository. The only knowledge that is therefore required to successfully extend Hyper is that of its underlying open source libraries. Instead of exposing a custom API method or parameter for every possible customization point, we allow you to intercept and compose every bit of functionality! The extension system is designed around composition of the APIs we use to build the terminal: React components and Redux actions. Available options are: true, false, "left"Įxtensions are universal Node.js modules loaded by both Electron and the renderer process. Available options are: true, falseĬhange the position/visibility of the window controls. If true, Hyper will be set as the default protocol client for SSHĬhange the behaviour of modifier keys to act as meta keyĬhange the visibility of the hamburger menu. If true, on right click selected text will be copied or pasted if no selection is present (true by default on Windows) If true, selected text will automatically be copied to the clipboard The number of rows to be persisted in terminal buffer for scrolling The default width/height in pixels of a new window The names of the keys represent the "ANSI 16", which can all be seen in the default config.Ī path to a custom shell to run when Hyper starts a new sessionĪn object of environment variables to set before launching shell hyper.js and add it to plugins module.exports = Ī list of overrides for the color palette. We encourage everyone to include hyper in the keywordsfield in package.json. ExtensionsĮxtensions are available on npm. In the future, we anticipate the community will come up with innovative additions to enhance what could be the simplest, most powerful and well-tested interface for productivity. In the beginning, our focus will be primarily around speed, stability and the development of the correct API for extension authors. The goal of the project is to create a beautiful and extensible experience for command-line interface users, built on open web standards.
0 kommentar(er)
