Package Exports
- create-emotion
- create-emotion/dist/create-emotion.browser.cjs.js
- create-emotion/dist/create-emotion.browser.esm.js
- create-emotion/dist/create-emotion.cjs.js
- create-emotion/dist/create-emotion.esm.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (create-emotion) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
create-emotion
Create distinct instances of emotion.
The main emotion package can be thought of as a call to createEmotion
with sensible defaults for most applications.
import createEmotion from 'create-emotion'
export const {
flush,
hydrate,
cx,
merge,
getRegisteredStyles,
injectGlobal,
keyframes,
css,
sheet,
cache
} = createEmotion()
Upside
Calling it directly will allow for some low level customization.
Create custom names for emotion APIs to help with migration from other, similar libraries.
Could set custom
key
to something other thancss
Downside
Introduces some amount of complexity to your application that can vary depending on developer experience.
Required to keep up with changes in the repo and API at a lower level than if using
emotion
directly
Primary use cases
Using emotion in embedded contexts such as an
<iframe/>
Setting a nonce on any
<style/>
tag emotion creates for security purposesUse emotion with a developer defined
<style/>
tagUsing emotion with custom stylis plugins
Multiple instances in a single app example
import createEmotion from 'create-emotion'
export const {
flush,
hydrate,
cx,
merge,
getRegisteredStyles,
injectGlobal,
keyframes,
css,
sheet,
cache
} = createEmotion({
// The key option is required when there will be multiple instances in a single app
key: 'some-key'
})
Options
createEmotion
accepts the same options as createCache from @emotion/cache
.