-
Notifications
You must be signed in to change notification settings - Fork 167
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
[BUG] Hot reload issues with Vaadin 14.7.0 #11888
Comments
Thanks for using Vaadin Platform, we appreciate your help and are going to take care of this as soon as possible. |
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888 Co-authored-by: caalador <[email protected]>
Do not mark pin if no version is actually added or changed. With this npm install will not always be executed on reload and the copied modules will not disappear. Fixes #11888 Co-authored-by: caalador <[email protected]>
This ticket/PR has been released with platform 21.0.2. |
When it will be backported to Vaadin 14? |
It will be out in the next maintenance release of v14.7 |
This ticket/PR has been released with platform 14.7.1. |
This ticket/PR has been released with platform 22.0.0.alpha5 and is also targeting the upcoming stable 22.0.0 version. |
This ticket/PR has been released with platform 20.0.8. |
Describe the bug
Hot reload with spring-boot-devtools result in failed to import frontend dependencies
To Reproduce
Steps to reproduce the behavior:
mvn spring-boot:run
or RunApplication.java
HelloWorldView.java
(e.g. 'Hello' to 'Hi')Expected behavior
Should rebuild then start the app normally, this method previously work well with Vaadin 14.4.7
Screenshots
Desktop:
Additional context
Have upgraded from Vaadin 14.4.7 to 14.7.0 then try above method as usual and the error appeared. I am curious whether there is startup configuration change in new version so try it with fresh download but unfortunately that happend too.
The text was updated successfully, but these errors were encountered: