-
Notifications
You must be signed in to change notification settings - Fork 24
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
Introduce @feature-hub/react
package
#30
Milestone
Comments
Good idea, a context provider/consumer should probably also be part of that package. |
Yes, but that could mean that we might need to support ES modules again because of code splitting. |
clebert
added a commit
that referenced
this issue
Nov 23, 2018
clebert
changed the title
Introduce
Introduce Nov 24, 2018
@feature-hub/react
package@feature-hub/react-components
package
clebert
changed the title
Introduce
Introduce Nov 26, 2018
@feature-hub/react-components
package@feature-hub/react
package
clebert
added a commit
that referenced
this issue
Nov 26, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should offer a React package. This includes both React components and the React Node.js integrator. This will replace the existing React packages.
The text was updated successfully, but these errors were encountered: