search

eirslett / frontend-maven-plugin

"Maven-node-grunt-gulp-npm-node-plugin to end all maven-node-grunt-gulp-npm-plugins." A Maven plugin that downloads/installs Node and NPM locally, runs NPM install, Grunt, Gulp and/or Karma.
Apache License 2.0
4.26k stars 872 forks source link

Yarn proxy issue #695

Open tschaka1904 opened 6 years ago

tschaka1904 commented 6 years ago

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: screen shot 2018-02-23 at 12 20 57

What is the expected behavior? I can in the: screen shot 2018-02-23 at 12 22 30

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 commented 3 years ago

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: ```

yarn check 
                    <goals>
                        <goal>yarn</goal>
                    </goals>
                    <phase>test</phase>
                    <configuration>
                        <arguments>run check</arguments>
                        <environmentVariables>
                            <CI>true</CI>
                        </environmentVariables>
                    </configuration>
                </execution>```
mshepel commented 3 years ago

It's resolved in version 1.12.0

mvrueden commented 2 years ago

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