Guy Bedford

@arhart sure, if you're after an explicit suggestion I can certainly provide that. My simplified or recommended pattern for implementation would be: ``` node --ceiling-path="./app" --ceiling-path="./" ``` Possibly alternatively supporting...

> I wouldn't characterize this feature as specifying path(s) within which Node.js should execute code. Instead, I'd say it's about stopping module resolution at particular path(s). In both forms, it...

@achingbrain thanks for your work in looking into this, these are really important numbers to track. If we had had benchmarks to compare, we may have been able to catch...

Perhaps this default with an environment variable to customize makes sense. Definitely seems a useful feature.

It seems this is primarily because `path.extname('.js') === ''`. `require('./.mjs')` or `require('./.js')` in type module also might not work as expected either (possibly misdetecting and falling back to cjs?).

Thanks for picking this problem up. Agreed having it not apply to `.mjs` and `.cjs` would be odd, and that needs to be addressed. I do still think there might...

I'm not sure exactly which timing Matteo is referring to, but in the initial loaders PR, we attempted to make loaders apply for all module loads, but had to back...

Involvement in standards should be a goal IMO. I think it would help to see Beaker as part of an ecosystem of new browser development work, along with other projects...

The PR in https://github.com/rollup/plugins/pull/1196 should fix these I believe?

I'm happy to review any PR work here, it would be great to see this supported.