You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In comparing the dimport legacy importer with Chrome's native importer, I am noticing a discrepancy in how paths are resolved.
In chrome, I see the following happening...
Given the following structure:
/index.html
/foo/main.js
/foo/dynamic-component.js
if /foo/main.js has the following code
import('./dynamic-component.js');
Chrome loads the file fine. When testing in Firefox using the legacy importer it is looking for the file in /dynamic-component.js instead of /foo/dynamic-component.js and 404s. I haven't tested the module/nomodule versions to see if there is any difference with them.
The text was updated successfully, but these errors were encountered:
In comparing the dimport legacy importer with Chrome's native importer, I am noticing a discrepancy in how paths are resolved.
In chrome, I see the following happening...
Given the following structure:
/index.html
/foo/main.js
/foo/dynamic-component.js
if /foo/main.js has the following code
Chrome loads the file fine. When testing in Firefox using the legacy importer it is looking for the file in /dynamic-component.js instead of /foo/dynamic-component.js and 404s. I haven't tested the module/nomodule versions to see if there is any difference with them.
The text was updated successfully, but these errors were encountered: