Error when project is being rebuilt

So, I’ve had this happen a couple of times in the past, with it eventually just going away, but I thought I might as well ask.
Whenever spring devtools (or my IDE? I’m not 100% sure) reloads/rebuilds my project it suddenly starts to throw the same exact error every time.

Failed to load "./index" from "src/main/frontend/generated/vaadin.ts". Does the file exist?

Like I said above this has haunted me occasionally in the past, especially whenever I upgrade my Vaadin version. It has been like that from 14.x.0 to 14.x.1, from 14 to 23, etc.

Whenever it starts the first time the generated folder looks like this:
image

and right after the stuff rebuilds it throws an error:

22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -  ERROR(TypeScript)  Cannot find module 'Frontend/generated/flow/generated-flow-imports.js' or its corresponding type declarations.
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -  FILE  V:/Suwayomi/VaaUI/src/main/frontend/generated/flow/Flow.tsx:28:27
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - 
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -     26 |
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -     27 | const flow = new _Flow({
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   > 28 |     imports: () => import("Frontend/generated/flow/generated-flow-imports.js")
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -        |                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
22:41:11.408 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -     29 | });
22:41:11.409 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -     30 |
22:41:11.409 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -     31 | const router = {
22:41:11.409 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - 
22:41:11.409 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - [TypeScript] Found 1 error. Watching for file changes.

and the files in the folder look like this:

image

Is there anything known about this weird bug, because it is really annoying waiting for it to just magically disappear eventually.

My project can be found here if you need to repro this:
https://github.com/Suwayomi/Suwayomi-VaadinUI/tree/notifications

And here’s the full log that is being output whenever I try to access the site after the rebuild:

22:31:39.996 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - [vite] Pre-transform error: Failed to load url /generated/vite-devmode.ts (resolved id: /generated/vite-devmode.ts). Does the file exist?
22:31:40.015 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - [vite] Pre-transform error: Failed to resolve import "./index" from "src/main/frontend/generated/vaadin.ts". Does the file exist?
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker - [vite] Internal server error: Failed to resolve import "./index" from "src/main/frontend/generated/vaadin.ts". Does the file exist?
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   Plugin: vite:import-analysis
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   File: V:/Suwayomi/VaaUI/src/main/frontend/generated/vaadin.ts:32:7
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   26 |  import "@vaadin/icon/vaadin-icon.js";
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   27 |  import "./vaadin-featureflags.js";
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   28 |  import "./index";
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -      |          ^
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   29 |  import "./vaadin-react.js";
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -   30 |  import "Frontend/generated/jar-resources/vaadin-dev-tools/vaadin-dev-tools.js";
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at TransformPluginContext._formatError (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:49746:41)
22:31:40.580 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at TransformPluginContext.error (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:49741:16)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at normalizeUrl (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:64331:23)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:64463:39
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async Promise.all (index 21)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async TransformPluginContext.transform (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:64390:7)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async PluginContainer.transform (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:49587:18)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async loadAndTransform (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:52409:27)
22:31:40.581 [dev-server-output] INFO  c.v.b.d.DevServerOutputTracker -       at async viteTransformMiddleware (file:///V:/Suwayomi/VaaUI/node_modules/vite/dist/node/chunks/dep-CzJTQ5q7.js:62173:24)

Couple quick things you can do are

Delete folder src/main/frontend/generated

run “mvn vaadin:clean-frontend”

And try again.

I tried this, albeit I replaced the maven command with gradle’s vaadinClean command. Unfortunately this didn’t seem to change anything about the issue, anything else I could try?

So, after some further testing, it seems that somewhere between 24.4.1 and 24.4.6 this has become consistent for me to show up, whenever I change the version from 24.4.1 to 24.4.6 (or 24.4.7) the project won’t work correctly anymore and throw the aforementioned error logs. Not sure what that means exactly, but I thought I might as well mention it