relative path approach

[bourgeoa]

The issue is that you need different publicPaths for different deployments. The solution is to use relative paths in the HTML and set publicPath: '':

Now with publicPath:'' and relative paths (./mashlib.js), the chunks will load relative to wherever the HTML file is:

✅ http://alice.localhost:3000/browse.html → loads ./mashlib.js and ./841.mashlib.js
✅ https://solidos.github.io/mashlib/dist/browse.html → loads ./mashlib.js and ./841.mashlib.js
Rebuild with npm run build and both scenarios should work!

With publicPath: '', HtmlWebpackPlugin will inject <script src="mashlib.min.js"></script> (relative path without the ./ prefix, which is equivalent).

The generated databrowser.html will have relative paths for all assets, just like browse.html now does. Both work the same way.With publicPath: '', HtmlWebpackPlugin will inject <script src="mashlib.min.js"></script> (relative path without the ./ prefix, which is equivalent).

The generated databrowser.html will have relative paths for all assets, just like browse.html now does. Both work the same way.

Claude Son