I have modules that do not export es6 style but need to be transformed

[elevatebart]

Why limit the transforms to files that contain import and exports ES6 style like so ?

if(isEs6(context.js.ast)){
    ...
}

Why not simply babel every file ?
I am trying to use the delay library in a Karma-Typescript context and the testing returns a parsing error at bundling even with your transform.

Can you help me figure it out ?

[erikbarke]

Hey @elevatebart, I'll take a look!

[elevatebart]

I was even nicer, I created a pull request #2.
Hope you like it ;-)

[erikbarke]

Thanks!! Unfortunately #2 broke a lot of things including the integration tests in karma-typescript... I've improved the ES6 detection by looking for more keywords recursively and I have a successful integration test in karma-typescript locally that requires the delay module.

Does it work for you too if you install the latest from master, npm i github:monounity/karma-typescript-es6-transform?
If you’re behind a firewall and can’t install from GitHub, you can download the branch as a zip and install manually.

[elevatebart]

Do you know where I could have access to these integration tests so that I can make sure that my branch does not break them before I go ahead and submit anything else. The first issue with delay was the use of an arrow expression () => 'the return';

[elevatebart]

Just to be clear, your changes fixed my initial issue which was to be able to use 'delay'.
But if the module I import from npm is built as follows

module.export = () => {
    return "test";
}

the bundling will probably fail.

[erikbarke]

Ok, I've added support for fat arrow functions too with a unit test containing your example!
Also, the integration tests are referenced above if you want to take a look.
Thanks for reporting this and coming up with suggestions 😃

[elevatebart]

it's working like a charm !!! thank you !!!

[elevatebart]

We tested it on our side and we love it. The last thing we need is npm publish and we are all set !!!
Do not forget to increase the minor package number ;-).

Once this is done, you can close the issue.

[erikbarke]

On npm now!