You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 12, 2021. It is now read-only.
Describe the bug
I am using Vaadin 14.3.4 with compatibility mode. It works fine in development mode, but when I try to run production mode, vaadinTranspileDependencies fails with the following error message
Task :web:vaadinTranspileDependencies
Performing annotation scan...
Returning default whitelisted packages...
Scanning with whitelist:
.
.
.
Scan completed.
Javascript modules is not supported in compatibility mode.
The following classes contains @JSModule annotations
.
.
.
Please use HTML imports instead.
I am not using @JsModule anywhere in my code. However, all the mentioned classes with error do extend Vaadin components. For example. Vaadin-Dialog version 2.2.1 and Vaadin-Details version 2.1.0
Same project is working with Vaadin version 14.0.5 and Vaadin Gradle plugin 1.3.5
To Reproduce
Steps to reproduce the behavior:
Setup project with Vaadin 14.3.4 and compatibility mode
Extend Vaadin components to implement a custom component
Run ./gradlew vaadinTranspileDependencies
Expected behavior vaadinTranspileDependencies should run successful and application should run in production mode
The text was updated successfully, but these errors were encountered:
Shridhad
changed the title
vaadinTranspileDependencies fails for @JsModule
vaadinTranspileDependencies fails for @JsModule, even if its not used
Sep 13, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
**Desktop
Describe the bug
I am using Vaadin 14.3.4 with compatibility mode. It works fine in development mode, but when I try to run production mode,
vaadinTranspileDependencies
fails with the following error messageI am not using
@JsModule
anywhere in my code. However, all the mentioned classes with error do extend Vaadin components. For example.Vaadin-Dialog
version 2.2.1 andVaadin-Details
version 2.1.0Same project is working with Vaadin version
14.0.5
and Vaadin Gradle plugin1.3.5
To Reproduce
Steps to reproduce the behavior:
./gradlew vaadinTranspileDependencies
Expected behavior
vaadinTranspileDependencies
should run successful and application should run in production modeThe text was updated successfully, but these errors were encountered: