The following workflow seems to work:
- Activate the conda environments for development commands and for the JupyterLab server (once).
jupyter labextension devel . --overwrite (once) in the repository directory.
- Make change to index.ts (iteratively).
jlpm run build (iteratively).
- Reload JupterLab in the browser and observe change (iteratively).
It is my understanding, at present, that that workflow is sufficient for extensions that run in the browser, however it may not be sufficient for server extensions.
There is a statement in Developing a prebuilt extension that I find confusing: “While authoring a prebuilt extension, you can use the
labextension develop command to create a link to your prebuilt output directory, similar to
pip install -e.”
That statement seems to indicate to me that
jupyter labextension devel . --overwrite can be used in place of
pip install -e.
Extension development is one of the primary activities that I will be working on in a job that I started last week. I would like to help with the extension documentation, however I need to develop a better understanding of the development process.