Stuck on an issue?

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.

"Could not locate bower" error while migrating from Vaadin 13 to Vaadin 14

See original GitHub issue

“Could not locate bower” error while migrating from Vaadin 13 to Vaadin 14

Error while migrating from Vaadin 13 to Vaadin 14 using migration tool

Running mvn vaadin:migrate-to-p3 -Dresources=<RESOURCES_PATH> -X error com.vaadin.flow.migration.MigrationToolsException: Could not locate bower. Install it manually on your system and re-run migration goal

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:11 (9 by maintainers)

Top GitHub Comments

1reaction

vaadin-mikicommented, May 13, 2020

reopening this issue, as it still exists and disables migrating from v10 to v14 for Windows users

known workaround is to install Linux subsystem, install bower and run migration there; another workaround suggests using docker, installing bower and running migration there - I think these are not acceptable as solutions

a look into the code seems to indicate that migration tool looks for bower in an empty directory if it is not installed globally, but that is just my guess based on the fact that I have not written that code and I have no idea how it works

0reactions

mvysnycommented, Aug 18, 2020

Still not fixed in Vaadin 14.3.3. The WSL workaround is not a solution - the WSL is quite slow; the migration might require recompiling the entire app under WSL which can be tedious (1h+). Also not a workaround for WIndows folk who do not know anything about linux.