jupyterlab-nebari-mode

Nebari customizations for JupyterLab.

Plugins

jupyterlab-nebari-mode:logo: replaces @jupyterlab/application-extension:logo, adding clickable Nebari logo:
jupyterlab-nebari-mode:commands adds the following commands:
- nebari:open-proxy which opens proxied processes, such as VSCode; this command can be used to add a menu entry, e.g.:
```
{
"command": "nebari:open-proxy",
"rank": 1,
"args": {
"name": "vscode"
}
}
```
- nebari:run-first-enabled which runs the first available and enabled command; it differs from the built-in apputils:run-first-enabled command in that it takes a list of objects representing the commands, allowing to customise the label, iconClass, caption, usage, and className properties. An example usage for menu customization would be adding a menu entry labelled Import numpy in File Editor when user has the File Editor open and Import numpy in Notebook when user has a Notebook open:
```
{
"command": "nebari:run-first-enabled",
"rank": 1,
"args": {
"commands": [
  {
    "id": "fileeditor:replace-selection",
    "label": "Import numpy in File Editor",
    "args": { "text": "import numpy as np" }
  },
  {
    "id": "notebook:replace-selection",
    "label": "Import numpy in Notebook",
    "args": { "text": "import numpy as np" }
  }
]
}
}
```

Requirements

JupyterLab >= 4.0.0

Install

To install the extension, execute:

pip install jupyterlab_nebari_mode

Uninstall

To remove the extension, execute:

pip uninstall jupyterlab_nebari_mode

Contributing

Development install

Note: You will need NodeJS to build the extension package.

The jlpm command is JupyterLab's pinned version of yarn that is installed with JupyterLab. You may use yarn or npm in lieu of jlpm below.

# Clone the repo to your local environment
# Change directory to the jupyterlab_nebari_mode directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm build

You can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.

# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab

With the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).

By default, the jlpm build command generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:

jupyter lab build --minimize=False

Development uninstall

pip uninstall jupyterlab_nebari_mode

In development mode, you will also need to remove the symlink created by jupyter labextension develop command. To find its location, you can run jupyter labextension list to figure out where the labextensions folder is located. Then you can remove the symlink named jupyterlab-nebari-mode within that folder.

Testing the extension

Frontend tests

This extension is using Jest for JavaScript code testing.

To execute them, execute:

jlpm
jlpm test

Integration tests

This extension uses Playwright for the integration tests (aka user level tests). More precisely, the JupyterLab helper Galata is used to handle testing the extension in JupyterLab.

More information are provided within the ui-tests README.

Packaging the extension

See RELEASE

nebari-dev / jupyterlab-nebari-mode

readme