Closed rsynek closed 2 years ago
Faced a similar problem while working with yarn run
Looks like yarn use npm registry property... https://github.com/eirslett/frontend-maven-plugin/blob/master/frontend-maven-plugin/src/main/java/com/github/eirslett/maven/plugins/frontend/mojo/YarnMojo.java
@rsynek Looks like there is WA:
1) pom file:
`
`
2) package.json file:
"scripts": { "build:prod": "{ng build --configuration production}" },
magic in {ng build --configuration production}
instead ng build --configuration production
Bugfix is coming in this PR: https://github.com/eirslett/frontend-maven-plugin/pull/1013
https://github.com/eirslett/frontend-maven-plugin/pull/1013 merged; closing this issue.
Do you want to request a feature or report a bug? Bug
What is the current behavior? The plugin adds
--registry
as an argument of the commandnpx
is supposed to execute. The build fails as the command does not recognize the--registry
option.If the current behavior is a bug, please provide the steps to reproduce.
npx
, e.g.:mvn generate-resources -DnpmRegistryURL=https://some.repository.org
error: unknown option '--registry=https://some.repository.org'
asantora
does not recognize the--registry
option.What is the expected behavior? The plugin should prepend the
npx
arguments before the command, see https://docs.npmjs.com/cli/v7/commands/npx#npx-vs-npm-exec. However, the--registry
option does not seem to be supported bynpx
anyway.Please mention your frontend-maven-plugin and operating system version. 1.12.0 Ubuntu 20.04.3 LTS