Split react-components into core and pro parts #5204
Labels
Comments
mshabarov
moved this from 🪵Product backlog
to 🟢Ready to Go
in Vaadin Flow ongoing work (Vaadin 10+)
|
Created the React components split PR: vaadin/react-components#242 |
caalador
added a commit
to vaadin/flow
that referenced
this issue
Apr 4, 2024
Extend the test so that we test using react-components-pro from the vaadin-versions.json file. Remove unused parameter. part of vaadin/platform#5204
|
Flow will pick/discard react components by the mode flag ("mode": "react") in the versions files and both Extended test to check this case explicitly: vaadin/flow#19103 |
|
i have pushed a branch in platform with the necessary changes. let us wait after beta |
tltv
pushed a commit
to vaadin/flow
that referenced
this issue
Apr 8, 2024
Extend the test so that we test using react-components-pro from the vaadin-versions.json file. Remove unused parameter. part of vaadin/platform#5204
9 tasks
|
Done. Tested with having |
github-project-automation
bot
moved this from 🟢Ready to Go
to Done
in Vaadin Flow ongoing work (Vaadin 10+)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe your motivation
Vaadin Core / open source users should be able to use core/free React components without Vaadin license.
Describe the solution you'd like
Acceptance Criteria:
@vaadin/react-components(free) and@vaadin/react-components-pro(commercial) npm packages, this change is re-appliedreact-componentsincoreandreact-components-proinvaadin@vaadin/react-components-propackage intopackage.jsoninvaadindependency is used in a project.@vaadin/react-componentsare added for bothvaadin-coreandvaadin.Note: this is planned between 24.4 beta and GA, so that these changes don't block beta release and beta testing.
Describe alternatives you've considered
No response
Additional context
Vaadin 24.4.
The text was updated successfully, but these errors were encountered: