I now have it building with webpack-macros.html disabled:
https://salsa.debian.org/rnpalmer-guest/pydata-sphinx-theme/-/tree/fix1084781?ref_type=heads
However, I don't know how much functionality this loses (beyond that
only test_translations fails). Hence, I don't know whether the best
option is this incomplete 0.15, going back to 0.7 (again), or not using
this theme at all. (I chose not using this theme at all for my latest
pandas upload, but mostly because it was the one I could do right now.)
I didn't manage to get webpack to find the installed Javascript packages
(see the history of the above branch for what I tried). Notes for any
future attempt:
- Some other packages successfully use webpack (
https://codesearch.debian.net/search?q=%28%5E%7C%5B+%2C%5D%29webpack+path%3Adebian%2Fcontrol&literal=0
), so looking at them and/or using pkg-js-tools might help. However, no
other Debian package appears to use sphinx-theme-builder or nodeenv
(heat-dashboard and masakari-dashboard say they build-depend on nodeenv
but don't appear to actually run it).
- I suspect the error message
"/builds/rnpalmer-guest/pydata-sphinx-theme/debian/output/source_dir/src/node_modules
doesn't exist or is not a directory" isn't actually accurate; it appears
to come from
https://sources.debian.org/src/node-enhanced-resolve/5.15.0-1/lib/ModulesInHierarchicalDirectoriesPlugin.js/?hl=75#L75,
so adding some debug prints there might be a good investigation method.
We would probably also need to package some more Javascript modules:
node-sass (RFP #998024; that suggests that rsass or node-node-sass
*might* be an alternative), node-sass-loader, and newer versions of
libjs-popper.js and node-mini-css-extract-plugin.