Vaadin 24.4.alpha25 project gets stuck in an infinite reload loop with VS Code

[marcushellberg]

Description of the bug

When starting a new Vaadin 24.4.alpha25 application in VS Code, it gets stuck in an infinite reload cycle caused by:

Change set: [/Users/mhellber/Desktop/my-app/target/classes [/Users/mhellber/Desktop/my-app/target/classes/META-INF/resources/images/empty-plant.png (MODIFY), /Users/mhellber/Desktop/my-app/target/classes/META-INF/resources/icons/icon.png (MODIFY), /Users/mhellber/Desktop/my-app/target/classes/banner.txt (MODIFY)]]

Running VS Code extension bisect, I could identify the extension causing the issue as the RedHat Java plugin.

Expected behavior

The application should start normally.

Minimal reproducible example

An application downloaded with https://start.vaadin.com/dl?preset=react&preset=partial-prerelease using alpha25.
Starting the app with VS Code running (either by running Application.java or with mvn) causes the app to reload constantly.

Versions

• Vaadin / Flow version: 24.4.alpha25
• Java version: OpenJDK Runtime Environment GraalVM CE 22+36.1 (build 22+36-jvmci-b02)
• OS version: macOS 14.4.1
• IDE (if applicable): VS Code 1.88.1
• Language Support For Java by RedHat VS Code extension version 1.30.0

[mshabarov]

I couldn't reproduce it.
Tried running the app by running Application.java and mvn.
Also tried disable/enabled the extension, works without restarts.

My configuration:

VS Code Version: 1.88.1 (also tried with 1.87)
Chromium: 120.0.6099.291
Node.js: 18.18.2
OS: Darwin x64 22.3.0
JDK 21
Language Support for Java(TM) by Red Hat v1.30.0

[manolo]

I cannot reproduce this either, with the same setup, except that my operating system is ventura 13.1 i7

[AlainaFaisal]

I reproduced this case and it stuck in an infinite loop for me as well.
However, after looking at the error logs, I saw some deprecated packages. These changes worked for me:
Change this to latest in package-lock.json:
"@jridgewell/sourcemap-codec": "latest",

(Also check if node.js is installed or not, you can install it from https://nodejs.org/)
After that ensure your versions are up to date using:
npm install -g npm@latest

These steps resolved the issue on my side.

[codercodingthecode]

See this temporary solution vaadin/hilla#2573 (comment)