For better separation of concerns, would it be better for the relevant code to be contributed upstream to nbconvert itself or a separate package?
I assume this repo deals mostly with Javascript "frontends", and e.g. JupyterLab users should not have to install a collection of legacy notebook extensions to get nbconvert functionality.
I work in JupyterLab and use the
html-embed
option in nbconvert when exporting notebooks into a standalone HTML file. However it seems that the extensions to nbconvert that allow this are bundled together with this package: https://github.com/ipython-contrib/jupyter_contrib_nbextensions/tree/master/src/jupyter_contrib_nbextensions/nbconvert_supportFor better separation of concerns, would it be better for the relevant code to be contributed upstream to nbconvert itself or a separate package?
I assume this repo deals mostly with Javascript "frontends", and e.g. JupyterLab users should not have to install a collection of legacy notebook extensions to get nbconvert functionality.