It seems, that there are still some imports left in code, that have no exact extensions. This is not supported by node module resolution process:
Node API - file extensions
Why and where it is usually a problem ?
When running otel-cf-workers code not in the bundled form (together with worker code), particularly in unit tests.
Why it is not noticable and was not mentioned a lot of times before ?
I think, that is exactly due to the previous point: running a Cloudflare worker (even locally) usually includes a bundling step, by esbuild. And, possibly, exactly the bundler solves all the problems with having incorrect import signatures.
But, when writing unit-tests for the workers (if you do not use a bundle at all), that becomes a problem - and module resolutions fails with console errors (in my case, it is the mocha framework):
Important - this is a direct continuation of a previously raised issue:
ESM interoperability question, which as I think, was closed without a real resolution (unfortunately). I also think, we need to re-think and fix all issues mentioned in that issue.
It seems, that there are still some imports left in code, that have no exact extensions. This is not supported by node module resolution process: Node API - file extensions
Why and where it is usually a problem ?
When running otel-cf-workers code not in the bundled form (together with worker code), particularly in unit tests.
Why it is not noticable and was not mentioned a lot of times before ?
I think, that is exactly due to the previous point: running a Cloudflare worker (even locally) usually includes a bundling step, by esbuild. And, possibly, exactly the bundler solves all the problems with having incorrect import signatures.
But, when writing unit-tests for the workers (if you do not use a bundle at all), that becomes a problem - and module resolutions fails with console errors (in my case, it is the mocha framework):
Important - this is a direct continuation of a previously raised issue:
ESM interoperability question, which as I think, was closed without a real resolution (unfortunately). I also think, we need to re-think and fix all issues mentioned in that issue.