- CLI can now run with only
@twilio/flex-plugin
and moving unused dependencies todevDependencies
reducing bundle size and fixing major security issues
- Fixed plugin release issue from non-plugin folders.
- Fixed warnings and errors on babel/plugin-proposal-private-property-in-object.
- Fixed cli issue when used in
yarn workspaces
- Fixed plugin istall issue, where it installs v6.4.2 instead of latest if no version is specified on install script.
- Fixed node version incompatibility issue due to cheerio package dependency, users with node version less than 18.17, can use without any issues.
- Upgraded paste versions of plugin template to fix conflict warnings
- Fixed the failed to load remote plugins issue when using
--include-remote
flag
Refer to Twilio Flex Docs to be up-to-date with the latest features being built on the CLI.
Flex Plugin CLI can now help users validate their plugin against the latest Flex UI version to ensure compatibility between the two.
- New command added -
twilio:flex:plugins:validate
. More details here. - Validation of the plugin runs as part of the
twilio:flex:plugins:deploy
command. - Telemetry integration for all the commands.
- Fixed high security vulnerabilities by upgrading Webpack Dev Server to v4.
- Enhanced the CLI version update notifier feature and added deprecation notification as part of it so that the user can always be on the stable version of the CLI.
- Removed unused dependencies in @twilio/flex-plugin-scripts package.
Install the Twilio CLI and the Flex Plugins extension as described here. Then go to the plugin directory and run:
$ twilio flex:plugins:upgrade-plugin --install
This script should automatically upgrade your plugin to the latest version.
To manually upgrade to version 7.x, modify your package.json
:
{
"scripts": {
"postinstall": "flex-plugin pre-script-check"
},
"dependencies": {
"flex-plugin-scripts": "^7.0.0",
"react": "17.0.2",
"react-dom": "17.0.2"
},
"devDependencies": {
"@twilio/flex-ui": "^2"
}
}
Version 7 is dropping support for Node 14. This means that the plugin would also have to be compatible with Node 16.x onwards.