frontend compilation fails after upgrading to vaadin 23.1.0
See original GitHub issueDescription of the bug
After upgrading to vaadin 23.1.0 I ran:
rm -rf target rm -rf node_modules npm i mvn install
When I try to restart tomcat I get the following error:
13 12:57:22,617 http-nio-8080-exec-1 USER: [ERROR] (CustomExceptionHandler.java:36) - Uncaught UI exception
[m java.lang.IllegalStateException: Startup of Webpack failed. Output was:
[webpack-cli] TypeError: cli.isMultipleCompiler is not a function
at Command.<anonymous> (/home/bsutton/git/onepub/onepub_vaadin/node_modules/.pnpm/@webpack-cli+serve@1.7.0_8b27d5839a2bdf89ba2338e4c89fea10/node_modules/@webpack-cli/serve/lib/index.js:146:35)
at async Promise.all (index 1)
at async Command.<anonymous> (/home/bsutton/git/onepub/onepub_vaadin/node_modules/.pnpm/webpack-cli@4.9.2_9c3dcbfb57ee5c2fcb4d4b626946cc9c/node_modules/webpack-cli/lib/webpack-cli.js:1674:7)
at com.vaadin.base.devserver.AbstractDevServerRunner.doStartDevModeServer(AbstractDevServerRunner.java:219) ~[vaadin-dev-server-23.1.0.jar:?]
at com.vaadin.base.devserver.AbstractDevServerRunner.runOnFutureComplete(AbstractDevServerRunner.java:171) ~[vaadin-dev-server-23.1.0.jar:?]
at com.vaadin.base.devserver.AbstractDevServerRunner.lambda$new$0(AbstractDevServerRunner.java:162) ~[vaadin-dev-server-23.1.0.jar:?]
at java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:863) ~[?:?]
at java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:841) ~[?:?]
at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:483) ~[?:?]
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373) ~[?:?]
at java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182) ~[?:?]
at java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655) ~[?:?]
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622) ~[?:?]
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165) ~[?:?]
Expected behavior
tomcat should start without an error.
Minimal reproducible example
After upgrading to vaadin 23.1.0 I ran:
rm -rf target rm -rf node_modules npm i mvn install
Versions
- Vaadin / Flow version: 23.1.0
- Java version: OpenJDK 64-Bit Server VM (build 17.0.3+7-Ubuntu-0ubuntu0.22.04.1, mixed mode, sharing)
- OS version: Ubuntu: 22.04
- Browser version (if applicable):
- Application Server (if applicable): Apache Tomcat/9.0.36
- IDE (if applicable): eclipse
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:21 (12 by maintainers)
Top Results From Across the Web
Vaadin upgrade 22.0.2 to 23.0.3 failed - Stack Overflow
Never mind - I did a "Vaadin dance" and then the build worked. And the application - at least on first sight -...
Read more >Vaadin 14 to 23 Upgrade Instructions
This is a list of the changes you need to make in your application when upgrading it from Vaadin 14 to Vaadin 23,...
Read more >Releases | Vaadin
Vaadin 23. Vaadin 23 is the latest stable version released under the new simplified release model. This is the recommended version for all...
Read more >Can't resolve '@vaadin/flow-frontend/flow-component-renderer
Hi, I have a Vaadin 14 app, and I keep getting the following error when deploying my app in wildfly: ERROR in ../target/frontend/generated-flow-imports.js ......
Read more >Vaadin 23 is finally here!
Download and configure a new Vaadin 23 app or read the upgrade guide ... for more control over what to display when form...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Instead of downgrading, maybe upgrading is easier
This issue has been fixed in V23.1.1, V23.0.12 and V22.0.17.
Vaadin 14.8 and 10.0 have no such an issue.
Please let us know if you still experience any issues with
webpack-cli
by commenting to this ticket or creating a new one.