Thoughts on separating pure UI jupyterlab-extensions from script dependencies?

[ianhi]

When I open a notebook I pretty much always want to have jupyterlab-vim and jupyterlab-code-formatter available to me. But these are purely for developer experience, no one I will then send the notebook too would need these installed. Is there an easy way to mark them as separate but still easily accesible to me? Almost like an extra dep for UI

something like:
juv run notebook.ipynb --with ui-deps

# /// script
# requires-python = ">=3.11"
# dependencies = [
#   "requests<3",
#   "rich",
# ]
# jupyterlab-ui = [
#  "jupyterlab-vim",
# ]
# ///

[ianhi]

Or I guess alternatively I would love to be able to set a global juv config that would automatically add those to my envinroments but not encode them in notebooks

[manzt]

I'm also a huge fan of jupyterlab-vim (thank you!). This flow is currently supported using the --with flag like in uv.

Most of my juv usage looks like this:

juv run --with=jupyterlab-vim foo.ipynb

you can pass comma separated or multiple with arguments:

juv run --with jupyterlab-vim,other-dep --with another-dep foo.ipynb

I'm open to thinking about some configuration for something like this in some "tool" metadata (which could be configured/specific to a runtime):

[tool.juv.lab]
extras = ["jupyterlab-vim"]

But haven't found the current (--with) usage to be very cumbersome for myself. I'd like to avoid mechanisms of imparting my ui-specific preferences on others, which inline-metadata could make a problem. A global config could be an option, but again... I haven't found the current too burdensome.

[manzt]

something like:

juv run notebook.ipynb --with ui-deps

This usage works as well!