admin管理员组

文章数量:1279118

When I build for production mode with Vaadin 24.6.5 and then check the build artifacts, I find that the frontend component versions are lagging behind. All the backend Jars have version 24.6.5, but in package.json:

"@vaadin/bundles": "24.6.4", "@vaadin/react-components": "24.6.4" and so forth - all components are lagging one version behind. The same is true for pnpm-lock.yaml

When I downgrade to 24.6.4, the same thing happens: the backend jars are all 24.6.4 and the frontend components are then 24.6.3.

When I build for production mode with Vaadin 24.6.5 and then check the build artifacts, I find that the frontend component versions are lagging behind. All the backend Jars have version 24.6.5, but in package.json:

"@vaadin/bundles": "24.6.4", "@vaadin/react-components": "24.6.4" and so forth - all components are lagging one version behind. The same is true for pnpm-lock.yaml

When I downgrade to 24.6.4, the same thing happens: the backend jars are all 24.6.4 and the frontend components are then 24.6.3.

  • vaadin
  • vaadin-flow
Share Improve this question asked Feb 24 at 11:11 ulimulim 1731 silver badge16 bronze badges
Add a comment  | 

1 Answer 1

Reset to default 0

This is not always the case; I happened to have a Vaadin 24.5.0 project open and it has, for example, "@vaadin/bundles": "24.5.0" and "@vaadin/polymer-legacy-adapter": "24.5.0" in package.json. I believe the reason behind "lagging" client-side versions is just that there's not always a need to publish a new version, especially if there are no relevant changes.

本文标签： Why are Vaadin frontend component versions lagging behind the backend versionsStack Overflow

版权声明：本文标题：Why are Vaadin frontend component versions lagging behind the backend versions? - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1741274672a2369658.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。