Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Yarn 1.0.0 has moved it's executable path from yarn/dist/bin/yarn to yarn/yarn-<version>/bin/yarn
See original GitHub issueDo you want to request a feature or report a bug? Bug
What is the current behavior?
Fails to execute. target/node/yarn/dist/bin/yarn doesn’t exist and the following maven error appears.
Cannot run program "target/node/yarn/dist/bin/yarn" (in directory "src/main/webapp"): error=2, No such file or directory
If the current behavior is a bug, please provide the steps to reproduce.
- Set
yarnVersiontov1.0.0in configuration - Run
yarngoal - Inspect
target/node/yarndirectory fordist/bin/yarn - Instead find
bin/yarn
What is the expected behavior?
Runs yarn executable correctly (maybe through user config or version matching).
Please mention your frontend-maven-plugin and operating system version. Plugin version: 1.3 Linux Mint 18.3
Issue Analytics
- State:
- Created 6 years ago
- Reactions:21
- Comments:20 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ok, I finally got time to release it now! I just had to tweak some environment variables related to som TTY in order to make the GPG sign command work. Should be synced to Central soon.
it does not seem to work for me still, I am using version 1.6 of the plugin