Artur

To be clear: I am not actually sure that this lib is broken but using testcontainers brings this in and this in turns brings an old JNA that breaks e.g....

It looks like the project is missing the exclusion of development only artifacts from the production build. Try adding this to the pom.xml https://github.com/vaadin/skeleton-starter-hilla-react/pull/219/files

> The library purpose is to establish serial communication, and the basis for that is the notifications mechanism, so how would you implement it differently? I know I am (ab)using...

Go ahead. I used the TS version and made some small fixes there also

This seems to work but I hope there is a better way: ``` Design.setComponentFactory(new DefaultComponentFactory() { @Override public Component createComponent(String fullyQualifiedClassName, DesignContext context) { Class

This is still an issue. With a fresh Mars.2, Vaadin plug-in 3.0 you get "An internal error occurred during: "Creating vaadin-archetype-application"" ``` java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.plexus.archiver.jar.JarArchiver at jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(java.base@9-ea/Native...

Thanks but I don't think we can remove our custom version and upgrade because of #53/#54

Selenium downloads and uses the correct webdriver automatically through its Selenium Manager since maybe a year or so. Does it not work on Linux?

Running a start.vaadin.com test on Vaadin 16 sometimes fail with the following screenshot.  Isn't this a really fundamental problem that will break all...

I can reproduce this on a Mac by 1. Taking the default starter application 2. Wait for output to say "Starting webpack-dev-server" 3. Press ctrl-s to stop the console output,...