TLDR - styles are still loaded even when the lab extension is disabled and Jupyterlab's --future-skip-styles-for-disabled flag is used.
Jupyterlab 3.6.0 recently introduced an option --future-skip-styles-for-disabled to avoid loading styles of disabled extensions. This flag is about to become the default in Jupyterlab 4.0 - see section "Future changes" here. This is a much-anticipated step in addressing the performance issues of Jupyterlab.
However, when I disable jupyter-vuetify and start Jupyterlab 3.6.1 using the flag described above, I can see that the styles of this extension are still loaded onto the page, since the styles are loaded directly in this line - link while Jupyterlab's recommendation seems to be to define the location of CSS in package.json - link
Seeing this is incompatible with a Jupyterlab option that is about to become default, can this be fixed please?
TLDR - styles are still loaded even when the lab extension is disabled and Jupyterlab's
--future-skip-styles-for-disabledflag is used.Jupyterlab 3.6.0 recently introduced an option
--future-skip-styles-for-disabledto avoid loading styles of disabled extensions. This flag is about to become the default in Jupyterlab 4.0 - see section "Future changes" here. This is a much-anticipated step in addressing the performance issues of Jupyterlab.However, when I disable
jupyter-vuetifyand start Jupyterlab 3.6.1 using the flag described above, I can see that the styles of this extension are still loaded onto the page, since the styles are loaded directly in this line - link while Jupyterlab's recommendation seems to be to define the location of CSS in package.json - linkSeeing this is incompatible with a Jupyterlab option that is about to become default, can this be fixed please?