Investigate using webpack 5 auto public path #9043

jasongrout · 2020-09-19T03:32:52Z

Right now, we have a solution for setting the public path in a compiled extension that involves writing some modules at compile time, etc. It works, but it's a bit of a hack, both in the writing of the modules and in how they are included in the module federation bundle.

In webpack/webpack#11258 (webpack 5.0b32), and interesting "auto" option is introduced. We may be able to use it.

This removes a hardcoded assumption about where the lab extensions live in the server url namespace, making things more flexible for the future. Fixes jupyterlab#9043

jasongrout added the enhancement label Sep 19, 2020

jasongrout added this to the 3.1 milestone Sep 19, 2020

jasongrout changed the title ~~Webpack 5.0b32 has auto public path that we might use~~ Investigate using webpack 5 auto public path Sep 19, 2020

jasongrout modified the milestones: 3.1, 3.0 Sep 19, 2020

jasongrout added this to To do in Extension System rework via automation Sep 19, 2020

jasongrout mentioned this issue Sep 23, 2020

Use the new webpack 5 ‘auto’ publicPath #9062

Merged

jasongrout closed this as completed in #9062 Sep 24, 2020

Extension System rework automation moved this from To do to Done Sep 24, 2020

github-actions bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Mar 24, 2021

github-actions bot locked as resolved and limited conversation to collaborators Mar 24, 2021

Investigate using webpack 5 auto public path #9043

Investigate using webpack 5 auto public path #9043

Comments

jasongrout commented Sep 19, 2020 • edited

jasongrout commented Sep 19, 2020 •

edited