Package Exports
- @naavre/containerizer-jupyterlab
- @naavre/containerizer-jupyterlab/lib/index.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@naavre/containerizer-jupyterlab) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
NaaVRE_containerizer_jupyterlab
NaaVRE cells containerizer frontend on Jupyter Lab
Requirements
- JupyterLab >= 4.0.0
Install
To install the extension, execute:
pip install NaaVRE-containerizer-jupyterlab
Uninstall
To remove the extension, execute:
pip uninstall NaaVRE-containerizer-jupyterlab
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 NaaVRE_containerizer_jupyterlab directory
# Create a virtual environment and activate it
virtualenv venv
. venv/bin/activate
# Install jupyterlab and refresh the virtual lab
pip install 'jupyterlab>=4.0.0,<5'
. venv/bin/activate
# 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
This extension communicates with external NaaVRE services. During development, you can run a local version of those services with Docker compose. Initial setup:
- Create a file
./dev/containerizer-config.json
by copying./dev/containerizer-config-example.json
and fill-in values forcell_github_url
,cell_github_token
, andregistry_url
. To obtain these values, create your own cells repository from the NaaVRE-cells template, and follow instructions from the readme. - Copy the Jupyter Lab configuration
mkdir venv/share/jupyter/lab/settings/ cp dev/overrides.json venv/share/jupyter/lab/settings/
- Start docker compose
docker compose -f dev/docker-compose.yaml up
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
while read env; do export $env; done < ./dev/jupyterlab.env
jupyter lab --notebook-dir ./notebook-dir
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 NaaVRE-containerizer-jupyterlab
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 @naavre/containerizer-jupyterlab
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