caalador

In this insance going to robots.txt with the browser returns 404 with the no route exception page, for using curl the returned page is the BrowserNotSupported which is a 200...

If the browser details for google bot say it supports es6 then it shouldn't get the unsupported page as that is where the curl request failed I guess as it...

For 17 it seems like the request is handled by `IndexHtmlRequestHandler`

I at least couldn't replicate the issue where memory would be used up with any noticable rate with the given project. Only difference in environments would be that I'm still...

It should be trying to read `@JsModule` and `@JavaScript` annotations and imports in `generated-flow-imports.js` and `generated-flow-imports-fallback.js` (these 2 should match `@NpmPackage` found in the code). Then it checks for these...

Test with 21.0.2 as it should be fixed with vaadin/flow#11853 as was for vaadin/flow#11910

Fusion has added quite a lot of steps to the webpack build slowing it down from what it was in v14 Also just having a look at the report the...

Also see work done for v19: vaadin/flow#10281

@hlbp This sounds like a Spring(-boot) issue. Try starting with `mvn spring-boot:run -Pproduction` (or add the `build-frontend` goal to the vaadin plugin to get pseudo dev mode running) and see...

running the application with `vaadin.useDeprecatedV14Bootstrapping=true` You get ``` HTTP/1.1 404 Set-Cookie: JSESSIONID=96321ACDFA9EB15253FB7B639D3ACEC5; Path=/; HttpOnly Cache-Control: no-cache, no-store Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT Content-Type: text/html;charset=utf-8 Transfer-Encoding: chunked...