Jacob Smith

I switched to [`ts-loader`](https://github.com/TypeStrong/ts-loader), and the problem solved itself.

@dancon that couldn't be the cause as merely switching loaders resolves this. This was quite a while ago though, so maybe it's fixed by now.

~I couldn't get it to work with alias + cwd either (I always get `Error [ERR_MODULE_NOT_FOUND]: Cannot find package`).~ Nevermind. It was a problem with babel-register.

I think a glob would an ideal solution: * It is very common in test runners (I can't think of any test runner that does not support it), so users...

Perhaps `node:fs`? ```js import { glob } from 'node:fs/promises'; const [ file1, file2, ...files ] = await glob('./src/**/*.spec.mjs'); ``` As for the team, I imagine it depends on where it...

> Or we could keep the test runner minimalistic, and let user land build on top of it to add more complex missing features. I think this is theoretically a...

> Your implementation seems to split the loaders in two, but doesn't entirely answer the requirement to "leverage loaders when resolving subsequent loaders". Ahhh, yes: ambient loaders need to be...

`` as a wrapper is working for me (React 16.2.0 & Enzyme 3.3.0): ```jsx const wrapper = shallow(); console.log( wrapper.debug(), wrapper.children().debug(), ); ``` log output: ```jsx ``` Which is exactly...

Hmm, if you're running it via mocha directly, I presume you've installed mocha globally? That could make a huge difference (and is unlikely to be an uncommon real-world scenario). I...

I took a quick gander at [@babel/register](https://github.com/babel/babel/blob/main/packages/babel-register/src/node.js) hoping there was something quick I could glean and incorporate from that, but it's much more involved than I was hoping ☹️