New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching between pnpm and npm is broken on first try when cleaning the project #11177
Comments
The issue is with To be tested with commons-io 2.9.0 if it fixes the issue, as flow is using And for some reason, I was not able to anymore get the project to fail when going from npm -> pnpm. |
Needs a re-check because commons-io has been upgraded in Flow to 2.11.0, so this issue might be fixed by this upgrade. |
This is still broken in commons-io 2.11.0 and Vaadin 22.0.0.rc1
|
To reproduce:
vaadin.pnpm.enable =false
toapplication.properties
mvn clean
Steps 3+4 can be combined with
mvn clean spring-boot:run
.Expected: project works
Actual: npm/pnpm install fails due to missing
target/flow-frontend/package.json
Rerunning the project will work.
It seems that there is some broken logic in
but neither of these are a problem because they just make the
TaskGeneratePackgeJson
always create the file, but in the end something is still removing it, - investigation to be continued.The text was updated successfully, but these errors were encountered: