Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CCDM: no way to use exported webcomponents #7559

Closed
manolo opened this issue Feb 13, 2020 · 2 comments · Fixed by #7614
Closed

CCDM: no way to use exported webcomponents #7559

manolo opened this issue Feb 13, 2020 · 2 comments · Fixed by #7614
Assignees
Labels

Comments

@manolo
Copy link
Member

manolo commented Feb 13, 2020

Generated bundle in client-side mode is not able to import flow exported webcomponents since it takes as entry the frontend/index.ts file that loads asynchronously the generated target/frontend/generated-flow-imports

Possible solution is to deliver two bundles: vaadin-bundle.js and vaadin-wc.js, the first used in the IndexHtmlRequestHandler and second in the WebComponentBootstrapHandler

A workaround for having flow IT's passing is to have a custom index.ts file with just a line import '../target/frontend/generated-flow-imports'; but there is an issue related with this solution: vaadin/hilla#337

@manolo manolo added bug hilla Issues related to Hilla labels Feb 13, 2020
@Legioth
Copy link
Member

Legioth commented Feb 13, 2020

What is the use case, aside from our own ITs?

@manolo
Copy link
Member Author

manolo commented Feb 14, 2020

  • Given any Vaadin application that is exported the whole application as a webcomponent, it cannot be used from a 3rd party application importing it as a webcomponent. workaroune: needs to be run with the old bootstrap
  • Given a Vaadin application that can be used as a regular vaadin app including some client views, but it has exported sever views as webcomponents, it is imposible to use from a 3rd party app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants