-
Notifications
You must be signed in to change notification settings - Fork 190
fix: do not leak internally used dependencies to actual apps, not even as optionals #23011
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
fix: do not leak internally used dependencies to actual apps, not even as optionals #23011
Conversation
Some of the configs need to be reviewed, full build not done, opening draft PR for that...
mshabarov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have comments, looks fine. The question is shall we test it before merging, or shall we test with the alpha pre-release, which is easier. Merge and test sounds better to me.
…encies-leaking-from-vaadin-dev
|
…n as optionals (#23011) (#23152) Uses shade plugin to pull in some transitive dependencies to internal "flow-build-util" module. Although they are not ending up to the actual production artifact, they lower the DX as in IDE it may appear one has them evailable. Fixes #23007 Co-authored-by: Matti Tahvonen <matti@vaadin.com>
|
This ticket/PR has been released with Vaadin 25.1.0-alpha1. |



Uses shade plugin to pull in some transitive dependencies to internal "flow-build-util" module. Although they are not ending up to the actual production artifact, they lower the DX as in IDE it may appear one has them evailable.
Fixes #23007