-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
npm package doesn't include dist folder #3
Comments
Sorry about that 😅 This is fixed in 1.0.3 |
antongolub
added a commit
to antongolub-forks/emotion
that referenced
this issue
Mar 9, 2022
Andarist
added a commit
that referenced
this issue
Jun 12, 2022
…uldForwardProp` (#2333) * chore(style): let StyledOptions generic argument be optional * chore(native): let StyledOptions generic argument be optional * test(types): add tests for StyledOptions iface * feat(types): add keys assertion for StyledOptions generic * fix(styled): add StyledOptions type to CreateStyledComponent call signature fixes #2333 (comment) * test(styled): check type StyledOpts for composite component * test(styled): revert erroneous changes * test(styled): clarify StyledOptsBroken test case * test: refactor `styledOptions` generics tests * test: add more tests for StyledOptions * test: linting * test: tweak ups * feat: expose FilteringStyledOptions * fix: expost `FilteringStyledOptions` from native, tweak up some tests, add some comments * chore: use consistent default props type for both StyledOptions and FilteringStyledOptions * chore: snap #3 * styled.shouldForwardProp: require prop to be a string * Add PropertyKey->string changesets * Remove redundant `compilerOptions` * make `shouldForwardProp` always contravariant * Type fixes * Tweak `FilteringStyledOptions` and `StyledOptions` interfaces * Change `Props` constraint * Tweak type-level tests around `shouldForwardProp` * add changesets Co-authored-by: Sam Magura <[email protected]> Co-authored-by: Mateusz Burzyński <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I tried installing with both yarn and npm.
The text was updated successfully, but these errors were encountered: