Media state
Contains the central state of Media frontend
yarn add @atlaskit/media-state
1.5.1
Patch Changes
- Updated dependencies
Media State is a singleton package
Having multiple versions of Media State installed can result in potential issues, such as media preview failures.
You must ensure that your application dependencies only resolve to a unique package version, if you are:
- A platform consumer — i.e. you are using Media State directly in a npm package, for instance in a monorepo. Define Media State in your package.json file as a
peerDependency
anddevDependency
(for local testing). - A product consumer — i.e. you are working directly into your application. Define Media State in your package.json file as a direct dependency.
If you have any questions or need assistance in consuming this package correctly, please reach out to the #help-media-platform channel.
Internal Media Use Only
Media State is intended for internal use by the Media Platform and as a transitive dependency of a media package within your product.
Direct use of this component is not supported.
Consider using one of these packages instead:
Note: This component is designed for internal Atlassian development.
External contributors will be able to use this component but will not be able to submit issues.
This library provides a state management solution for Media frontend, particularly for caching the file states. It is built using Zustand and Immer, with devtools support for development environments.