Learning to see how its done to prep for client-side prolog. Some questions

This is sweet, really cool to see. A few questions for my learning and planning to take the prolog POC farther

1. In this line, the new Promise is constructed, but the first argument is named "reject", but this is still the resolve function, no? Have you renamed as per the intent, but functionally you are just returning the time out message?
https://github.com/exercism/js-test-runner-clientside/blob/5ee219716da41b9b36255a073c9740fba4e7cc3f/src/index.ts#L209

2. the `esm` templated string is brilliant, and when you import that, it then becomes an imported module file rather than loaded in to the global space. 🤩 🥇

2. You have a webpack comment on 156, is this because webpacker will try to re-write this concern to bundle it?
https://github.com/exercism/js-test-runner-clientside/blob/5ee219716da41b9b36255a073c9740fba4e7cc3f/src/index.ts#L156

Asking because I was planning to load the prolog wasm as it's bundled as its own package as well (https://www.npmjs.com/package/swipl-wasm) and its reasonably large (https://bundlephobia.com/package/swipl-wasm@5.0.11)

Start by reading src/index.ts at lines 156 and 209, then inspect the swipl-wasm package referenced in the discussion. The issue contains learning questions rather than a defined change, so clarify the intended Prolog POC scope and acceptance criteria before implementation can begin.

Written by the indexing model from the issue text.