Handle babel-node transcompilation

[jankoprowski]

Hi,

My protractor configuration and tests use babel-node to transcompile from ES6 to ES5.
I'm starting them like babel-node node_modules/.bin/protractor protractor.conf.js
However protractor-retry can't handle this and returns

[15:29:17] E/configParser - protractor.conf.js:13
import {BaseConf} from '../protractor.base.conf.js';
^^^^^^

This is caused by ES6 transcompiled by babel used in protractor configuration.
Is it possible to handle such case in protractor-retry?

[amrot17]

HI @jankoprowski

try to add this to the top of your protractor config . this should solve the issue

require("babel-core/register")({
  presets: ["env"]
});

[dreuxl]

@jankoprowski did it help?

[jankoprowski]

No it did not helped :(
I'm still getting:

[10:06:17] E/configParser - Error code: 105
[10:06:17] E/configParser - Error message: failed loading configuration file protractor.conf.js
[10:06:17] E/configParser - protractor.conf.js:13
import {BaseConf} from '../protractor.base.conf.js';
^^^^^^

SyntaxError: Unexpected token import

I have edited .babelrc to contain:

{
"presets": [
[
"env",
{
"targets": {
"esmodules": true
}
}
]
]
}

and

require("babel-core/register")({
presets: [["env", { "targets": { "esmodules": true } }]]
});

in protractor.conf.js

Now I'm getting:

import {BaseConf} from '../protractor.base.conf.js';
^

SyntaxError: Unexpected token {

[jankoprowski]

We abandoned babel, rewrote our test imports to NodeJS 10 and now tests are retrying successfully.
However now protractor retries all tests in all files instead only failures. I do not know why.