Skip to content
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

Version Packages (next) #1923

Merged
merged 1 commit into from
Aug 1, 2020
Merged

Version Packages (next) #1923

merged 1 commit into from
Aug 1, 2020

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jul 2, 2020

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, run changeset pre exit on next.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@emotion/jest@11.0.0-next.14

Major Changes

  • cd77efbf #1920 Thanks @Andarist! - The root entry (@emotion/jest) no longer has default and serializer exports. You can still import createSerializer 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's snapshotSerializers option, so it no longer has a default export - it only has test & serialize exports.. You can import createEnzymeSerializer 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's snapshotSerializers option, so it no longer has a default export - it only has test & serialize exports. You can import createSerializer from the root entry (@emotion/jest) and create your own serializer if needed.

Patch Changes

@emotion/styled@11.0.0-next.14

Minor Changes

  • 4d3b60d0 #1874 Thanks @connor-baer! - Added basic TS type support for as 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/react@11.0.0-next.14

@emotion/css@11.0.0-next.14

Patch Changes

  • 6d32d82b #1848 Thanks @osdiab! - Added speedy method to the TS type declaration of the sheet object available on Emotion instances. In addition to that - StyleSheet type is no longer exported from this package and instead CSSStyleSheet is available now. The StyleSheet type might still be imported from @emotion/sheet, but it has no speedy method and thus it's not the same as what is available in this package as CSSStyleSheet.

@emotion/native@11.0.0-next.14

Patch Changes

  • Updated dependencies []:
    • @emotion/primitives-core@11.0.0-next.14

@emotion/primitives@11.0.0-next.14

Patch Changes

  • Updated dependencies []:
    • @emotion/primitives-core@11.0.0-next.14

@emotion/primitives-core@11.0.0-next.14

Patch Changes

@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 for css prop has changed. Based on usage of our jsx pragma we are able to add support for css prop only for components that support className prop (as our jsx factory function takes provided css prop, resolves it and pass the generated className 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 the css prop when using different libraries with the css prop support, such as styled-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 the css prop globally, for all components. Use it like this:

    import {} from '@emotion/react/types/css-prop'

    In this particular case we are forced to extend the existing React.Attributes interface. Previously we've been extending both React.DOMAttributes<T> and JSX.IntrinsicAttributes. This change is really minor and shouldn't affect any consuming code.

  • Updated dependencies [4d3b60d0, 58dc08a6, 6d32d82b]:

    • @emotion/styled@11.0.0-next.14
    • @emotion/css@11.0.0-next.14
    • @emotion/server@11.0.0-next.14

@emotion/server@11.0.0-next.14

Patch Changes

  • Updated dependencies [6d32d82b]:
    • @emotion/css@11.0.0-next.14

@codesandbox-ci
Copy link

codesandbox-ci bot commented Jul 2, 2020

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 7399568:

Sandbox Source
Emotion Configuration

@github-actions github-actions bot force-pushed the changeset-release/next branch 2 times, most recently from 7e01036 to b89904a Compare July 2, 2020 21:52
@codecov
Copy link

codecov bot commented Jul 2, 2020

Codecov Report

❗ No coverage uploaded for pull request head (changeset-release/next@7399568). Click here to learn what that means.
The diff coverage is n/a.

@github-actions github-actions bot force-pushed the changeset-release/next branch 9 times, most recently from b6e6ab3 to 408dda5 Compare July 12, 2020 07:52
@github-actions github-actions bot force-pushed the changeset-release/next branch 2 times, most recently from 4a9b8b4 to feb9e5a Compare August 1, 2020 11:23
@Andarist Andarist merged commit 93c27e0 into next Aug 1, 2020
@Andarist Andarist deleted the changeset-release/next branch August 1, 2020 12:35
louisgv pushed a commit to louisgv/emotion that referenced this pull request Sep 6, 2020
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant