Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to next, this PR will be updated.
next
is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exit
onnext
.Releases
@emotion/jest@11.0.0-next.14
Major Changes
cd77efbf
#1920 Thanks @Andarist! - The root entry (@emotion/jest
) no longer hasdefault
andserializer
exports. You can still importcreateSerializer
from it to create your own serializer if needed.cd77efbf
#1920 Thanks @Andarist! -@emotion/jest/enzyme
entrypoint has been renamed to@emotion/jest/enzyme-serializer
. It's main purpose is compatibility with Jest'ssnapshotSerializers
option, so it no longer has a default export - it only hastest
&serialize
exports.. You can importcreateEnzymeSerializer
from the root entry (@emotion/jest
) and create your own serializer if needed.cd77efbf
#1920 Thanks @Andarist! -@emotion/jest/serializer
's main purpose is compatibility with Jest'ssnapshotSerializers
option, so it no longer has a default export - it only hastest
&serialize
exports. You can importcreateSerializer
from the root entry (@emotion/jest
) and create your own serializer if needed.Patch Changes
58dc08a6
,f57a7229
,6d32d82b
]:@emotion/styled@11.0.0-next.14
Minor Changes
4d3b60d0
#1874 Thanks @connor-baer! - Added basic TS type support foras
prop on styled components. It's possible to pass any component to it but it has no effect on other accepted props. This means that it's not 100% type-safe so use it sparingly and with care.Patch Changes
58dc08a6
#1837 Thanks @arcanis! - Fixed TS compatibility under PnP environments by making@types/react
an optional peer dependency.Updated dependencies [
58dc08a6
,f57a7229
]:@emotion/css@11.0.0-next.14
Patch Changes
6d32d82b
#1848 Thanks @osdiab! - Addedspeedy
method to the TS type declaration of thesheet
object available on Emotion instances. In addition to that -StyleSheet
type is no longer exported from this package and insteadCSSStyleSheet
is available now. TheStyleSheet
type might still be imported from@emotion/sheet
, but it has nospeedy
method and thus it's not the same as what is available in this package asCSSStyleSheet
.@emotion/native@11.0.0-next.14
Patch Changes
@emotion/primitives@11.0.0-next.14
Patch Changes
@emotion/primitives-core@11.0.0-next.14
Patch Changes
58dc08a6
,f57a7229
]:@emotion/react@11.0.0-next.14
Patch Changes
58dc08a6
#1837 Thanks @arcanis! - Fixed TS compatibility under PnP environments by making@types/react
an optional peer dependency.f57a7229
#1941 Thanks @Andarist! - The way in which we provide TypeScript support forcss
prop has changed. Based on usage of our jsx pragma we are able to add support forcss
prop only for components that supportclassName
prop (as ourjsx
factory function takes providedcss
prop, resolves it and pass the generatedclassName
to the rendered component). This has been implemented using technique described here. What is important - we no longer extend any global interfaces, so people shouldn't bump anymore into type conflicts for thecss
prop when using different libraries with thecss
prop support, such asstyled-components
.However, it's not possible to leverage
css
prop support being added conditionally based on a type of rendered component when one is not using our jsx pragma. For those cases when people use our pragma implicitly (for example when using our@emotion/babel-preset-css-prop
) we have added special file that can be imported once to add support for thecss
prop globally, for all components. Use it like this:In this particular case we are forced to extend the existing
React.Attributes
interface. Previously we've been extending bothReact.DOMAttributes<T>
andJSX.IntrinsicAttributes
. This change is really minor and shouldn't affect any consuming code.Updated dependencies [
4d3b60d0
,58dc08a6
,6d32d82b
]:@emotion/server@11.0.0-next.14
Patch Changes
6d32d82b
]: