Plugin API

User plugins are supported in the form of arbitrary js files, which can be loaded at runtime. Obviously, plugins should be loaded only from trusted sources, because they can run arbitrary code.

As plugins are loaded, they are transpiled with Babel using @babel/preset-env and @babel/preset-react. This enables plugin developers to use React to render custom UI, and use modern ES syntax.

Plugin files

A plugin file should export an object with the following keys:

Example of a complete plugin file:

module.exports = {
  name: 'test plugin',
  description: 'test plugin description',
  image: null,
  onLoad: api => {
    console.log('plugin started')

Uses the module.exports syntax to export your plugin so that Nuclear can access it. No other module syntax is supported at this time.

The API object

The plugin API that's passed to the plugin exposes the following keys:

Using React in plugins to render UI

It is possible to use React directly in plugins to render new UI elements. For example:

import React from 'react';
import ReactDOM from 'react-dom';

module.exports = {
  name: 'Navbar plugin',
  description: 'Creates a navbar under the main one',
  image: null,
  author: 'nukeop',
  onLoad: api => {

    const root = document.createElement('nav'); = 'plugin-root';
    const navbar = document.getElementsByClassName('navbar')[0];
    navbar.parentNode.insertBefore(root, navbar.nextSibling);

      <nav style={{padding: '1em'}}>Plugin navbar</nav>,

Removing plugins

After uninstlaling a plugin, its effects will remain until Nuclear is restarted or reloaded (ctrl+r).