Cannot update from 24.1.12 to 24.2.0, error during build frontend #17873
Labels
Comments
ElZorrito
changed the title
|
Ensure that your IDE doesn't cache the old java resources. Did you try a full clean install via command line? |
|
I'm experiencing the same. I've deleted node_modules before building my application based on 24.2.0. |
|
Deleting node_modules won't refresh your IDE's cache of java / dependencies classes. Ensure that all java dependencies have the correct version. As stated above, did it work by building the application via command line? |
|
Experienced the same today with 24.2.0 Compiling/running with jdk 17 on macOS M1 |
|
Same with me. Clean/clear doesn't seem to help. |
|
Based on the errors you provided, it seems like the older grid package version is installed that has no We will check that Flow Components use a correct version web components. Could you please meanwhile run with debug log level ( |
|
-X as parameter in the maven commandline? |
|
Yes, like |
|
Somewhere in the output it states: Is that the info you need? |
|
@wegerv you should also see something regarding npm packages, similar to this |
|
Hello, Thanks for your replies. All package are in good version : vaadin-grid-flow-24.2.0 for exemple. I have something like this with debug mode : |
|
@ElZorrito thanks for the logs provided. But is expected if you're using Vaadin 24.2.0. |
|
Could you guys check what version of |
|
I have |
|
And do you have |
Sorry I make a mistake, that's the log of another project in vaadin 24.1.12... sorry. To had this log I launched : mvn clean compile -P production -x I try same command with my project in 24.2.0 and I have this log : In |
|
@ElZorrito could you please post the full log? |
|
Yes, here he is : |
|
I'm experiencing this too. Tried removing "build","dev_bundle", "node_modules", "frontend/generated" to no avail. package.json has "24.2.0" versions |
|
For some reason, my Production version (build at 16:23) is working, but my Development version (build at 16:48) does not... |
|
@ElZorrito sorry to bother you, but we need a build with debug logs |
|
For more info: The log (interesting part..) of the (working) Production version: [INFO] --- vaadin-maven-plugin:24.2.0:prepare-frontend (default) @ trafficviewer-vaadin-framework --- [...] List of npm dependencies found in the project:
|
|
Comment is too long with full log, I put end here : |
|
Could you try to delete the pnpm caches? |
didn't work for me |
|
Suggestion with a configuration, I had never issues with:
|
|
@ElZorrito @wegerv @Siedlerchr @cassandrus could you please try switching from Looks like |
|
UPD: Vaadin 24.1.12 uses the same pnpm version, |
|
Tested upgrade from 24.1.12 to 24.2.0 on a clean environment. While using |
|
@ElZorrito @wegerv @Siedlerchr @cassandrus would be useful for us also to see what pnpm version you use in fact, is it a default one automatically used by Vaadin or installed by yourself? |
|
I delete node_module and replace package.json with older version (24.1.12) and add parameter I use default pnpm automatically used by Vaadin. |
|
pnpm default from vaadin as well |
|
@Siedlerchr works for you with |
|
Could you check if you have |
For me too |
For me too, thanks. |
|
A bit more context: The action proposed for Flow is to add this file into |
|
Deleting the .pnpmfile.cjs worked for me as well Edit// It was already in our .gitignore, I just had it locally still flying around from the previous version |
That would be a good fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
Hello,
I want to upgrade from 24.1.12 to 24.2.0 but there is an error when frontend is build :
I delete node_modules, package.json, pnpm-lock.yaml, vite.generated.ts and restart app, no effect.
Thanks
Expected behavior
Frontend build fine
Minimal reproducible example
I can't share my project
Versions
The text was updated successfully, but these errors were encountered: