Version Packages #2839
Merged
Version Packages #2839
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
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 b1aa274:
|
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
fb5bf85 to
5bf21cb
Compare
github-actions
bot
force-pushed
the
changeset-release/main
branch
from
5bf21cb to
b1aa274
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/babel-plugin-jsx-pragmatic@0.2.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/babel-preset-css-prop@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/cache@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79,bbad8c79]:@emotion/css@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79,bbad8c79]:@emotion/css-prettifier@1.1.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/eslint-plugin@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/hash@0.9.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/is-prop-valid@1.2.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/jest@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/memoize@0.8.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/native@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/primitives@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79]:@emotion/primitives-core@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/react@11.10.0
Minor Changes
#2819
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.#2819
bbad8c79Thanks @nicksrandall! - Thanks to the addedexportsfield, the package now includes aworkercondition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.Patch Changes
bbad8c79,bbad8c79]:@emotion/serialize@1.1.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
bbad8c79,bbad8c79]:@emotion/server@11.10.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.Patch Changes
#2835
fa7f494dThanks @manishco! - Added missing TypeScript declarations forextractCriticalToChunksandconstructStyleTagsFromChunksexports.Updated dependencies [
bbad8c79,bbad8c79]:@emotion/sheet@1.2.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/styled@11.10.0
Minor Changes
#2819
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.#2819
bbad8c79Thanks @nicksrandall! - Thanks to the addedexportsfield, the package now includes aworkercondition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.Patch Changes
bbad8c79,bbad8c79]:@emotion/unitless@0.8.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.@emotion/utils@1.2.0
Minor Changes
#2819
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.#2819
bbad8c79Thanks @nicksrandall! - Thanks to the addedexportsfield, the package now includes aworkercondition that can be utilized by properly configured bundlers when targeting worker-like environments. It fixes the issue with browser-specific files being prioritized by some bundlers when targeting workers.@emotion/weak-memoize@0.3.0
Minor Changes
bbad8c79Thanks @nicksrandall! -exportsfield has been added to thepackage.jsonmanifest. This fixes how our default exports are treated by Node.js when using their native support for ES modules. It also limits what files can be imported from a package but we've tried our best to allow importing all the files that were considered to be a part of the public API.