Repository navigation
Closed
Description
Description 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
Reacted by Christoph Frick, Philipp Dylong, FollowSteph, DMan and Adrián Szegedi
Activity
bsutton commentedon Jun 13, 2022
So I switched to vite (by manually configuring the properties file) which bypassed the above error.
However, I'm now getting the following error:
I have had this error with earlier versions of vaadin 23, but it seems to come and go.
bsutton commentedon Jun 13, 2022
Possibly helpful?
I have a file theme.js:
There is a largis generated file called
theme-OnePub.generated.js
And vaadin.ts contains:
bsutton commentedon Jun 13, 2022
I deleted frontend/generated.
After running mvn install I ended up with an index.ts which contained an error:
imports: () => import('../../target/frontend/generated-flow-imports')
The generated-flow-imports file doesn't exist.
bsutton commentedon Jun 13, 2022
I ignored the above error and tried to start tomcat.
I'm now getting:
caalador commentedon Jun 13, 2022
It would seem that webpack-cli 4.9 is not compatible with cli/serve 1.7 see webpack/webpack-cli#3294
As a workaround before a fix, defining the @webpack-cli/serve package.json dependency to v1.6.1 should fix the initial problem.
fix: Update webpack-cli to a latest version
fix: Update webpack-cli to a latest version (#13954)
fix: Update webpack-cli to a latest version (#13954)
fix: Update webpack-cli to a latest version (#13954)
enver-haase commentedon Jun 13, 2022
I had more luck with version 4.10.0 as in #13954.
9 remaining items
Artur- commentedon Jun 14, 2022
Instead of downgrading, maybe upgrading is easier
enver-haase commentedon Jun 14, 2022
it is
stefanuebe commentedon Jun 15, 2022
Since Vaadin 22 is also still maintained, we also need to provide the fix there.
stefanuebe commentedon Jun 15, 2022
Works also for Vaadin 22.
vaadin-bot commentedon Jun 16, 2022
This ticket/PR has been released with Vaadin 22.0.17.
enver-haase commentedon Jun 16, 2022
Dear Vaadin-Bot, which version is this in Vaadin 23 terms?
mstahv commentedon Jun 17, 2022
23.1.1 is fresh out of oven.
mshabarov commentedon Jun 17, 2022
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-cliby commenting to this ticket or creating a new one.mshabarov commentedon Jun 17, 2022
@bsutton could you create a separate ticket for the Vite errors you've experienced ?
I'm going to close this ticket.
bsutton commentedon Jun 17, 2022
vaadin-bot commentedon Jun 17, 2022
This ticket/PR has been released with Vaadin 23.1.1.
After updating to Vaadin 23 error occurred that caused system to fail.