Conversation
|
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. |
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
8225804 to
9bec0ba
Compare
Andarist
approved these changes
Nov 20, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 main, this PR will be updated.
Releases
@emotion/babel-plugin@11.13.5
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/cache@11.13.5
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/css@11.13.5
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/react@11.13.5
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/serialize@1.3.3
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/styled@11.13.5
Patch Changes
#3270
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.Updated dependencies [
77d930d]:@emotion/utils@1.4.2
Patch Changes
77d930dThanks @emmatown! - Fix inconsistent hashes using development vs production bundles/exportsconditions when using@emotion/babel-pluginwithsourceMap: true(the default). This is particularly visible when using Emotion with the Next.js Pages router where thedevelopmentcondition is used when bundling code but not when importing external code with Node.js.