Breaking Changes
Information about breaking changes.
- 1.
- 2.The behavior of the following plug-in commands were affected:
COMMAND | NOW | BEFORE |
plugin-list | It lists all the plug-ins installed for the application. | It listed all the plug-ins available in the compiler. |
plugin-install | It installs a plug-in and its dependencies. | Only the plugin's dependencies were installed, since the plug-in was embedded in the compiler. |
plugin-uninstall | It uninstalls a plug-in and its dependencies using npm. | Only the plugin's dependencies were uninstalled, since the plug-in was embedded in the compiler. |
plugin-info | It shows information about a plug-in installed for the application. | It shows information about a plug-in available in the compiler. |
plugin-serve | It starts a testing server using a plug-in installed for the application. | It started a testing server available in the compiler. |
No compatibility breaks.
External tools used by plug-ins are now installed locally, per project, instead of installed globally. Their direct execution (without using Concordia) is now possible through NPX. For instance, the command
codeceptjs run test.js must now be executed as npx codeceptjs run test.js. This change also allows the installation of different versions of external tools, when needed.- 1.Were there any changes in commands' syntaxes?No, there were not.
- 2.Is my configuration file still compatible?It depends. All the properties are still compatible, except for
"plugin". Whether your configuration file has that property, you should update it. - 3.Is it possible now to install or uninstall a plug-in with NPM ?Yes, it is possible to do both now.
Last modified 1yr ago