Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

Stripes Framework


Stripes framework is a collection of supporting modules for building a FOLIO user interface. Stripes wraps underlying stripes-* modules, defining dependencies on versions known to work well together. This takes the burden off app developers for selecting potentially incompatible versions of the underlying modules.


The modules included within Stripes are:

  • stripes-components -- A component library for Stripes
  • stripes-connect -- Manages the connection of UI components to back-end modules
  • stripes-core -- The core of Stripes, an opinionated and modular platform for React components consuming REST data and the UI framework for the FOLIO project
  • stripes-form -- A redux-form wrapper for Stripes
  • stripes-logger -- Simple category-based logging for Stripes
  • stripes-smart-components -- A suite of smart components. Each communicates with an Okapi web-service in order to provide the facilities that it renders
  • stripes-util -- A library of utility functions to support Stripes modules


Include stripes, as well as react, both as peerDependencies and devDependencies in your app's package.json. The peerDependency ensures the same version of stripes is shared across all apps when your app is included in a FOLIO platform. The devDependency enables your app to be built and run stand-alone with a version of stripes for development and testing.

  "devDependencies": {
    "@folio/stripes": "^1.0.0",
    "@folio/stripes-cli": "^1.5.0",
    "react": "^16.4.1",
  "peerDependencies": {
    "@folio/stripes": "^1.0.0"
    "react": "*"

Import your stripes-* dependencies, such as stripes-components, through the exports provided by stripes:

import {
} from '@folio/stripes/components';
import { AddressEditList } from '@folio/stripes/smart-components';

Note: Beginning with version 1.6, stripes-cli generates new apps using stripes framework.

Release procedure

When releasing a new version of stripes framework, follow the general release procedure for each of the individual stripes-* modules contained within stripes and for stripes itself. The following describes additional steps that should be taken into consideration when upgrading the framework and rolling it out to ui-modules and platforms.

Note: Until STRIPES-588 is addressed, if any one stripes-* module requires a major or minor version bump, then all stripes-* modules should receive a major or minor version bump. This avoids leaking dependencies from the new release into the old release which can lead to duplicate instances of stripes-components.

  • Update and release individual stripes-* modules.
    • Remember to update version numbers of any inter-stripes dependencies.
  • Update and release stripes framework.
    • Include links to stripes-* module changelogs in the stripes changelog.
  • Document ui-*/platform-* update procedure in the upgrade notes.
  • Update platform-* snapshot branches locally (peerDependency install warnings expected) and review any errors.
    • For an early check, do this before releasing stripes by pointing your local platform to the release branch of stripes.
    • Commit changes and release snapshot version when things look good.
    • Note: platform-complete snapshot depends on the snapshot release of platform-core.
  • Update and release ui-* module versions (if applicable, will be necessary for breaking changes).
  • Update and release other relevant platform-* branches (quarterly/master/next-release).
  • Update Stripes-CLI's ui-module blueprint to reference the new stripes-framework version, update the stripes-core version (if applicable), and release stripes-cli.

Upgrade notes

The following captures the general upgrade notes from one version of stripes framework to another. Take into account notes between your current version and the version to upgrade to. For instance, if upgrading from 1.0 to 2.0, review the steps for 1.1 and 2.0.

Migrating to v1.0

To migrate existing apps developed prior to the introduction of stripes framework, begin by adding stripes to your package.json as noted above.

Next, review all @folio/stripes-* imports replacing hyphens as necessary:

- import { Button } from '@folio/stripes-components';
+ import { Button } from '@folio/stripes/components';

Take care to remove any path-based imports you may have in the process:

- import Button from '@folio/stripes-components/lib/Button';
+ import { Button } from '@folio/stripes/components';

Review the stripes-components 4.x changelog for any breaking changes and moved components. Update affected imports to reflect their new component locations.

Finally remove all individual stripes-* dependencies from your app's package.json. Re-run your app to verify everything is working properly.

Upgrading to v1.1

Upgrading to stripes version 1.1.0, requires some minor adjustments to package.json. The process varies slightly for ui-modules and platforms.

To upgrade a ui-module, define any peerDependencies you may have on react, react-dom, react-redux, and redux also as devDependencies. This will ensure that these packages are properly fulfilled for isolated development and testing of your ui-module. Then upgrade your version of @folio/stripes to 1.1.0 in both devDependencies and peerDependencies.

"name": "@folio/ui-example",
"devDependencies": {
  "@folio/stripes": "^1.1.0",
  "@folio/stripes-cli": "^1.6.0",
  "react": "~16.6.3",
  "react-dom": "~16.6.3",
  "react-redux": "~5.1.1",
  "redux": "~3.7.2"
"peerDependencies": {
  "@folio/stripes": "^1.1.0",
  "react": "*",
  "react-dom": "*",
  "react-redux": "*",
  "redux": "*"

To upgrade a platform, add dependencies for react, react-dom, react-redux, and redux. This will ensure that these packages, defined as peerDependencies within ui-modules, are properly fulfilled at the platform level. Then upgrade your version of @folio/stripes to 1.1.0.

"name": "@folio/platform-example",
"dependencies": {
  "@folio/stripes": "^1.1.0",
  "@folio/stripes-cli": "^1.6.0",
  "react": "~16.6.3",
  "react-dom": "~16.6.3",
  "react-redux": "~5.1.1",
  "redux": "~3.7.2"

Finally, for both ui-modules and platforms, regenerate your yarn.lock file, if applicable.

Upgrading to v2.0

Review STRIPES-577 and the following changelogs for any breaking changes with your use of stripes-* dependencies. Breaking changes have been throwing deprecation warnings for some time, so these should not be new. Update usage of affected components if you haven't done so already.

For ui-* modules, upgrade your version of @folio/stripes from ^1.1.0 to ^2.0.0 in both devDependencies and peerDependencies.

For platforms, upgrade your version of @folio/stripes from ^1.1.0 to ^2.0.0 in dependencies.

For both ui-* modules and platforms, upgrade your devDependency of stripes-cli to ^1.8.0.

Upgrading to v2.6

For ui-* modules:

  • Upgrade your version of @folio/stripes from ^2.0.0 to ^2.6.0 in both devDependencies and peerDependencies.
  • Remove both path-based imports from @stripes-core:
- import setupStripesCore from '@folio/stripes-core/test/bigtest/helpers/setup-application';
+ import { setupStripesCore } from '@folio/stripes/core/test';


- import startMirage from '@folio/stripes-core/test/bigtest/network/start';
+ import { startMirage } from '@folio/stripes/core/test';
  • Remove @folio/stripes-core from devDependencies.