Create CSS bundle for @jupyter/theme-[light/dark]-extension

[SylvainCorlay]

It would be very useful if the unpkg distribution of theme-light-extension and theme-dark-extension included a CSS bundle inlining all the resources (images, urls.css, variables.css) to that it can be included as nbconvert inlining resources.

This is related to https://github.com/jupyterlab/jupyterlab/pull/6314, and such a bundle could be produced in the same way.

[blink1073]

I think that is better than adding a new no-op package to the core distribution.

[blink1073]

Unless you need both. 😁

[SylvainCorlay]

Unless you need both. :grin:

Yes, I think I need both.

It seems that theme-[light/dark]-extension version 0.19.1 has exactly what I need in the generated embed.css file, which is not generated anymore in 1.0.0-alpha.6.

[blink1073]

This PR removed the static css: https://github.com/jupyterlab/jupyterlab/pull/5505.
To bring it back, we'd have to reinstate the webpack config, deps and static files metadata in the packages, reinstate the build-themes.ts script, and run that script as part of prepublish.ts.

[jasongrout]

We could just build the embed css file to be in the published package without using it ourselves, and keep the existing streamlined build for jlab itself. So basically:

• webpack becomes a dev dependency for the themes
• the theme prepublish uses webpack to build the embed target
• the embed target result is included in the package
• perhaps the examples use it, or some use it, so we notice when something goes awry.

Is that what you were saying above, @blink1073? Or were you imagining us reverting to use the two-step webpack process for jlab itself?

[SylvainCorlay]

We could just build the embed css file to be in the published package without using it ourselves, and keep the existing streamlined build for jlab itself

That is exactly what I had in mind.

[blink1073]

Ditto

[SylvainCorlay]

Note: the same issue is coming up for other contexts than voila at the moment.