-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
CSS class names no longer working with 20.3.0 #1766
Comments
@mstanaland The "css injected prop" refers to the const { css, styles, theme} = withStylesProps();
return (
<WrappedComponent
{...this.props}
{...{
css,
styles,
theme,
}}
/>
); So there's no need to import Update: What surprises me is that this error wasn't happening before. Can you share the complete trace for that error? cc @ljharb |
@noratarano Sorry for the delay getting back to you, and thanks for the explanation - I think I follow now. A little more investigation on my part has me thinking the issue is likely at least partly our setup. We have react-dates in a component library that's used by multiple microservices. The 20.3.0 update seems to work fine in the component library itself; it's the microservices that are crashing. So maybe you can just close this issue, but I'm still scratching my head as to what the issue is though, since everything was A-OK with 20.2.5. Here's the error as Chrome spits it out
|
It might be that webpack’s automatic bundle splitting isn’t consistently deduping both react-dates and react-with-styles? |
I'm confirming there is still an issue in version 21.5.1. Following the install instructions results in a |
react-dates version
react-dates@20.3.0
Describe the bug
A project that was working with 20.2.5 using
react-dates/initialize
to get old-school class names is no longer working after upgrading to 20.3.0. Appears to be this PR: #1758Now getting the
Cannot read property 'createLTR' of undefined
like you got in the past if you didn't use initialize.Maybe this just needs documentation? Not sure what it meant by "css injected prop"
The text was updated successfully, but these errors were encountered: