Update plugins for Flex UI 2.x.x

Based on the implementation of your plugin, you may need to update your plugin source code and its dependencies to be compatible with Flex UI 2.x.x.

When you leverage the create command of the Flex Plugins CLI to create a new plugin, you need to update the dependencies on the package.json file of the plugin to make it compatible with 2.x.x.

Note the differences between the dependencies and devDependencies on the following sample package.json files. You need to update the devDependencies in order to run your plugin locally via the twilio flex:plugins:start command of the CLI.

1
{
2
 "name": "plugin-sample",
3
 "version": "0.0.0",
4
 "private": true,
5
 "scripts": {
6
   "postinstall": "flex-plugin pre-script-check"
7
 },
8
 "dependencies": {
9
   "@twilio/flex-plugin-scripts": "5.1.1",
10
   "react": "16.5.2",
11
   "react-dom": "16.5.2",
12
   "react-emotion": "9.2.12"
13
 },
14
 "devDependencies": {
15
   "@twilio/flex-ui": "^1",
16
   "react-test-renderer": "16.5.2"
17
 }
18

1
{
2
  "name": "plugin-sample",
3
  "version": "0.0.0",
4
  "private": true,
5
  "scripts": {
6
    "postinstall": "flex-plugin pre-script-check"
7
  },
8
  "dependencies": {
9
    "@twilio/flex-plugin-scripts": "5.1.2",
10
    "react": "17.0.2",
11
    "react-dom": "17.0.2",
12
    "prop-types": "^15.7.2",
13
    "@twilio-paste/core": "^15.3.0",
14
    "@twilio-paste/icons": "^9.2.0"
15
  },
16
  "devDependencies": {
17
    "@twilio/flex-ui": "^2",
18
    "react-test-renderer": "17.0.2"
19
  }
20
}
21

Following are some guidelines to help you manage the migration of your plugins:

1. Once you have updated your plugin code and dependencies to be compatible with 2.x.x, test your plugin locally by using the twilio flex:plugins:start command of the Flex Plugins CLI.
2. Once you have tested your plugin to ensure that it works as expected, deploy your plugin to your dev or staging environment using the twilio:flex:plugins:deploy command. We recommend following the Semantic Versioning format for managing your plugin version. Since this plugin is compatible with 2.x.x, we recommend registering this plugin version as a new major version. Use the --major argument and write a clear description for the Changelog of this version.
3. Enable the plugin deployed on your stage/dev account via the Plugins Dashboard or the Plugins CLI.
4. Follow Steps 1 to 3 for migrating all your plugins to be compatible with Flex UI 2.x.x.
5. Finally, create a release via the CLI or the Plugins Dashboard that contains all the plugins that you have migrated to 2.x.x. Leverage the description and the name fields to tag the release as being compatible with 2.x.x.