Lewis
Lewis
GitHub embeds it here as `ctjlewis/mocha:unload-files` and `ctjlewis:unload-files`. ![image](https://user-images.githubusercontent.com/1657236/104169975-035d2c80-53c6-11eb-9fa6-3f502d4ee842.png) I have no idea about the CI - I've never contributed to Mocha before, I just ran into this error and...
No worries @juergba, feel free to use this PR to debug.
@juergba Hey, any way I can help out here? This bug does actually break most `unloadFiles()` calls in ES contexts - not trying to be pushy at all, but I'm...
This PR fixes the issue. And yes but `unloadFiles`, which relies `unloadFile`, is public. I ran into this issue in real-world codebase, and resolving the import path works. Mocha is...
I guess the issue is not as obvious as I thought - I made a Repl.it here: https://repl.it/@christiantjl/MochaRequireResolve This basically only affects programs where we import Mocha from an ESM...
Tfw I *did* include a repro in that issue, and just recreated it a second time four days later... There are now *two* repros: 1. https://repl.it/@christiantjl/MochaRequireResolve 2. https://repl.it/@christiantjl/MochaFileUnloader I would...
Hate to bug you @juergba, but did you have a chance to review the example?
The run button doesn't work because of the Node version Repl.it uses by default (does not support ESM yet - see [How to import an ES module in Node.js REPL?](https://stackoverflow.com/a/54785616/1674992))....
CC: @boneskull @craigtaub @Munter @outsideris
I updated the Repl.it with a custom run command and `.mjs` extensions to get the repro to work with the Run button rather than needing to execute it directly: https://repl.it/@christiantjl/MochaRequireResolve