Issues using babel-typescript and @types packages about karma-rollup-preprocessor HOT 3 CLOSED

Ok, the error my issues was were caused by multiple parts:

1. Use the namedExports option to fix chai's exports.
2. Bug in this library:

On line 46 of lib/index.js, add:

const parsedPath = path.parse(file.path);
file.path = `${parsedPath.dir}/${result.fileName}`;

This is because the file path is still .ts after the bundle generation. It needs the extension to be renamed to js. This combines the new file name generated by rollup with the original directory given to karma.

I will try to put together a PR shortly!

from karma-rollup-preprocessor.

I am not 100% sure this is third party. I haven't had a similar issue or seen a similar issue in my research if, let's say, you would import chai in an application bundle. I can try to work on a reproduction from that standpoint tonight though.

from karma-rollup-preprocessor.

Generally speaking, this preprocessor is mostly a thin wrapper around the Rollup API, with most of its complexity coming from the custom file watcher. I am not 100% either, just suspicious since your error appears unrelated to API churn or the watcher.

My first guess is that this has something to do with config.files[0].module === true (L15), which I believe means Karma inserts <script type="module"> tags into the test document. Perhaps there is a conflict with that expectation of native ES modules and how babel is transpiling you modules?

from karma-rollup-preprocessor.