Upgrading 23.3 failed

Cannot find module ‘@vaadin/tooltip’ or its corresponding type declarations.

INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: ➜ Local: http://127.0.0.1:34393/VAADIN/
2022-12-16 08:25:53,670 INFO [ForkJoinPool.commonPool-worker-1] com.vaadin.base.devserver.AbstractDevServerRunner: Started Vite. Time: 1421ms
2022-12-16 08:25:56,188 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder:
2022-12-16 08:25:56,188 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: ERROR(TypeScript) Cannot find module ‘@vaadin/tooltip’ or its corresponding type declarations.
2022-12-16 08:25:56,189 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: FILE /frontend/generated/jar-resources/tooltip.ts:1:25
2022-12-16 08:25:56,189 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder:
2022-12-16 08:25:56,189 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: > 1 | import { Tooltip } from ‘@vaadin/tooltip’;
2022-12-16 08:25:56,190 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: | ^^^^^^^^^^^^^^^^^
2022-12-16 08:25:56,190 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: 2 |
2022-12-16 08:25:56,190 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: 3 | const _window = window as any;
2022-12-16 08:25:56,191 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: 4 | _window.Vaadin = _window.Vaadin || {};
2022-12-16 08:25:56,191 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder:
2022-12-16 08:25:56,191 INFO [dev-server-output] com.vaadin.base.devserver.DevServerOutputTracker$Finder: [TypeScript] Found 1 error. Watching for file changes.

Upgrading 23.3 failed

Did you do vaadin:dance before the update?

uf…no!

I’ll try it.

vaadin:dance resolved my problem! Thanks @quirky-zebra

Sounds like the upgrade with the stale resources from the previous version were the culprit. Cleaning up node_modules and other JS artefacts on version upgrades makes the process way more reliable in my experience (first start is kinda slow for downloading all stuff again, but it makes sure the latest and greatest is in use)