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
Currently, when a library uses the PathProvider helper component and depends on it, it also makes it mandatory to install the main @frctl/fractal package in an application that uses the library. This is because @frctl/react requires it as a peerDependency. This is unnecessary, since using only the helper component as a transitive dependency should not mandate using or installing the main Fractal module in an application.
What the feature should look like?
Split the components directory in the React adapter into another package, @frctl/react-components.
Keep the exports in the React package to provide backwards compatibility.
The text was updated successfully, but these errors were encountered:
What problem would this feature solve?
Currently, when a library uses the PathProvider helper component and depends on it, it also makes it mandatory to install the main
@frctl/fractal
package in an application that uses the library. This is because@frctl/react
requires it as a peerDependency. This is unnecessary, since using only the helper component as a transitive dependency should not mandate using or installing the main Fractal module in an application.What the feature should look like?
@frctl/react-components
.The text was updated successfully, but these errors were encountered: