Can't build and run after upgrade from Vaadin 17.0.11 to 18.0.1
See original GitHub issueDescription of the bug / feature
Problems after updating from Vaadin 17.0.11 to 18.0.1
When starting in developement mode I get the following error:
2020-12-02 12:57:31.870 ERROR 22416 --- [nio-8080-exec-1] c.v.flow.server.frontend.FrontendUtils : Cannot get the 'META-INF/VAADIN/index.html' from the classpath
2020-12-02 12:57:31.876 ERROR 22416 --- [nio-8080-exec-1] c.v.flow.server.DefaultErrorHandler :
java.io.UncheckedIOException: java.io.IOException: Failed to load content of './frontend/\/index.html'. It is required to have './frontend/\/index.html' file when using client side bootstrapping.
When building production image webpack throws the following error (starting Vaadin 18.0.x)
ERROR in ./styles/globalVariables.css
Module build failed (from ../node_modules/.pnpm/registry.npmjs.org/css-loader/4.2.1_webpack@4.42.0/node_modules/css-loader/dist/cjs.js):
Error: Can't resolve 'frontend/images/logo.svg' in 'D:\Workspace\webapp\frontend\styles'
Minimal reproducible example
My frontend folder looks like this:
frontent
- src
- styles
- index.html
In globalVariables.css
I have the following line:
--logoImage: url("frontend/images/logo.svg");
The logo is located in: webapp\src\main\resources\static\images\logo.svg
Expected behavior
No problem when running/building image
Actual behavior
Error when running/building image
Versions:
- Vaadin / Flow version: 18.0.1
- Java version: 11
- OS version: Windows 10
- Spring Boot: 2.4.0
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Can't build and run after upgrade from Vaadin 17.0.11 to 18.0.1
Problems after updating from Vaadin 17.0.11 to 18.0.1. When starting in developement mode I get the following error:
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 >Upgrading | Vaadin Docs
Show sub-pages of Step-by-step guide. Step-by-step guide · Importing to an IDE · Running an Application. Show sub-pages of Tutorial
Read more >Cant' build maven Base Starter project for Vaadin Flow
Hi, after downloading the zip and importing it (eclipse oxygen) as a maven project, I can't even compile. I get two errors :...
Read more >Build fails after upgrading from Vaadin 7 8
JavaCommand.execute(JavaCommand.java:330) at com.vaadin.integration.maven.CompileThemeMojo.processTheme(CompileThemeMojo.java:65) at ...
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 Free
Top 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
Thanks for the report - the untested workaround would be to add the following inside
webpack.config.js
before the linemodule.exports = merge(flowDefaults,
:we’ll land a fix for this soon that makes css-loader touch only
node_modules
urls.This has been fixed in 5.0.2 / 18.0.2