Importing npm modules as browserified js files works from an absolute path but not from a relative path

`

import mp from "./npm-modules/npm-mouse-position.js"
import mp2 from "https://lively-kernel.org/lively4/BP2019RH1/scratch/individualsAsPoints/regl/npm-modules/npm-mouse-position.js"

"mp:" + mp + " mp3: " + mp2
`

Gives this result when evaluated on a folder with an npm-modules subfolder which holds the nom-mouse-position.js file which can be found at https://lively-kernel.org/lively4/BP2019RH1/scratch/individualsAsPoints/regl/npm-modules/npm-mouse-position.js.


Reproduce the issue using the embedded script and the folder containing npm-modules/npm-mouse-position.js, comparing the relative import with the absolute URL shown in the report. Trace the browserified module loading path used for both cases. Done means the relative and absolute imports evaluate successfully in the same example.

Written by the indexing model from the issue text.