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
Debugging this further, I am seeing the following:
The dynamic import is transformed into const htmlAsString = await import("./ThemeChooser-YVQTYOLV.js"); inside ThemeChooser-QGTYAYZG.js.
Notice that the original import was for an HTML file but the bundled version is now referring to a JS file. Next, the html file is actually being bundled... but it's called ThemeChooser-R7JEJFRF.html. So it looks like the generated import statement is simply referring to the wrong filename.
I'm not sure how to debug this further without your help...
I suspect this plugin might have a problem with dynamic imports. Given
ThemeChooser.mts
that contains:I get this esbuild output:
Looking on disk,
ThemeChooser-QGTYAYZG.js
is created and referencesThemeChooser-YVQTYOLV.js
but the latter file does not exist.Do you have any idea why the file isn't being created? Maybe try adding a unit test for handling dynamic imports?
The text was updated successfully, but these errors were encountered: