Conversation
| "dependencies": {}, | ||
| "devDependencies": { | ||
| "vite": "5.3.1", | ||
| "vite": "5.3.2", |
There was a problem hiding this comment.
Off topic; just wanted to mention it here cause perfect place..
I noticed that when running clean install vaadin downgrades vite in 24.4 from 5.3.1 to 5.2.13 again.. once I start the application it's 5.3.1 again but it is really weird and always creates stale changes in git.
There was a problem hiding this comment.
Sounds completely off topic but is it vaadin:prepare-frontend that downgrades it? Sounds a bit like you somehow get an old Flow version on the classpath for the build part but when running the app you have the correct version
There was a problem hiding this comment.
Yeah prepare-frontend runs default. You are definitly correct with your assumption, only thing that made me question myself: No addons; just Vaadin 24.4 and dependency:tree looks good. Just wanted to mention it
There was a problem hiding this comment.
Might be that mvn dependency:resolve-plugins would show something else
There was a problem hiding this comment.
Sadly nothing really obvious; only thing that looked a bit off is the 24.4.1 of flow in 24.4.3 instead of the 24.4.2 mentioned in the release notes:
There was a problem hiding this comment.
The quickest fix for this issue is probably to pin Flow version in vaadin-maven-plugin, so it will at least be compatible with the platform.
Ping @ZheSun88
However, I suppose the proper solution would be making Flow maven plugin mojos be executed with project classpath instead of the plugin classpath, as discussed in #19010
|
* chore: Vite 5.3.2 * Update package.json
5 participants
No description provided.