Dynamic import() broken on Excalibur 0.25.1 and newer.

Steps to Reproduce

The attempt to use a dynamic import() as seen in @kamranayub’s CodeSandbox Example does not work after upgrading to/beyond 0.25.1, as it results in this error: TypeError: undefined is not a non-null object (Firefox) and TypeError: Object.defineProperty called on non-object (Chrome)

Here is a prepared CodeSandbox which showcases the issue: https://codesandbox.io/s/cool-ritchie-uu1m7v

Expected Result

Dynamic imports should work with the ESM bundle.

Actual Result

Attempting to use a dynamic import with 0.25.1 and beyond results in an error: TypeError: undefined is not a non-null object (Firefox) and TypeError: Object.defineProperty called on non-object (Chrome)

Environment

• browsers and versions: Chrome 108.0.5359.94, Firefox 107.0
• operating system: Mac OS 12.1
• Excalibur versions: ^0.25.1
• Works on 0.25.0 and older.

Current Workaround

N/A

[eonarheim]

@kamranayub Any initial ideas?

[kamranayub]

I’ve also updated the CodeSandbox so it’s working with this change.

@eonarheim Not sure what to do about this issue – UMD bundle will work fine, ESM works fine (I’m pretty sure) in other native ESM environments. So we may want to add a prominent note about Next.js support, or perhaps create a next-excalibur-plugin with a similar withExcalibur HOC like Preact does to wrap this logic (as having static file paths creates a coupling to our internals).