I’ve noticed something odd while working with Vaadin. After building my project in production mode using Vaadin 24.6.5, I checked the build output and found a strange version mismatch. All the backend JAR files show version 24.6.5, but the frontend components in package.json are stuck at 24.6.4. This includes things like @vaadin/bundles and @vaadin/react-components. The pnpm-lock.yaml file shows the same older version.
I tried downgrading to Vaadin 24.6.4 to see if it would fix the issue, but the same thing happened again. The backend JARs were 24.6.4, while the frontend components dropped to 24.6.3.
Is this normal behavior? If not, what could be causing this version lag between the frontend and backend components? Any insights would be really helpful!
i’ve seen this before. its probly a caching issue with the build system. try clearing ur project cache and run a clean build. if that doesn’t work, check ur maven/gradle config for any version overrides. sometimes theres a lag in syncing frontend n backend versions. good luck!
This version mismatch is actually a known behavior in Vaadin’s release cycle. The frontend components are typically released slightly before the backend components to ensure compatibility and stability. This staggered approach allows for thorough testing and integration before the full release.
It is not a bug or caching issue, but rather an intentional design decision. The backend version usually includes the most recent compatible frontend version. For further clarity or concerns regarding potential inconsistencies, referring to the official Vaadin release notes can provide detailed insights into the component versions and any specific considerations when upgrading.
hm, thats an interesting observation! have u checked the vaadin release notes? sometimes they mention these kinda quirks. maybe theres a specific reason for the version gap? it could be worth asking on the vaadin forums too - the devs might have more insight. what other odd things have u noticed while working with vaadin?