The module fallback service has some qwirky behaviors in regards to paths (that it provides and expects).
This requires consumer's code to be very careful and tweak the paths in and out[^examples]. Special care is needed to support different operative systems (windows being the odd one out).
This can be fidgety and annoying, we can probably make things better in the workerd layer itself, but before doing that we need to properly document and specify clearly what would be the ideal (or at least better) solution.
This issue is for the creation of such documentation that could be used to then spearhead/facilitate the appropriate changes in the workerd layer.
The module fallback service has some qwirky behaviors in regards to paths (that it provides and expects).
This requires consumer's code to be very careful and tweak the paths in and out[^examples]. Special care is needed to support different operative systems (windows being the odd one out).
[^examples]: examples of code requiring these extra tweaks: when extracting the received values, when redirecting, when returning a module
This can be fidgety and annoying, we can probably make things better in the workerd layer itself, but before doing that we need to properly document and specify clearly what would be the ideal (or at least better) solution.
This issue is for the creation of such documentation that could be used to then spearhead/facilitate the appropriate changes in the workerd layer.