Yarn proxy issue

[tschaka1904]

Do you want to request a feature or report a bug? Bug

What is the current behavior? Using install-node-and-yarn and yarnInheritsProxyConfigFromMaven and performing a eslint ./src/main/webapp/*/*.js leads to Invalid option '--https-proxy' - perhaps you meant '--parser'?

If the current behavior is a bug, please provide the steps to reproduce. Using this setup:

What is the expected behavior? I can in the:

add a <yarnInheritsProxyConfigFromMaven>false<yarnInheritsProxyConfigFromMaven/>, but this feels quite redundant. Maybe you should just be able to define where you want to use the proxy.

Please mention your frontend-maven-plugin and operating system version. Mac OS High Sierra 10.13.3

[andonu]

Managed to work around this by merging the test and lint goals together, it seems the plugin just appends the proxy args at the end. From package.json: "check": "eslint src --format table --ext .js,.jsx,.ts,.tsx --fix && react-scripts test --watchAll=false --passWithNoTests",

And in maven: <execution> <id>yarn check</id> <goals> <goal>yarn</goal> </goals> <phase>test</phase> <configuration> <arguments>run check</arguments> <environmentVariables> <CI>true</CI> </environmentVariables> </configuration> </execution>

[mshepel]

It's resolved in version 1.12.0

[mvrueden]

I stumbled upon this today and we are using 1.12.0. So it is still an issue.