Before starting the migration of your projects into Monaca, there are some key points you need to pay attention to in order to have a seamless migration.
Before getting started with the migration, you may want to know about the supported Cordova versions and build environments in Monaca.
All newly created projects in Monaca will be using the latest supported Cordova version by default.
Windows platform (electron)
For more information on build environments for lower Cordova versions, pleaser refer to Supported Environments.
In Monaca, the Cordova plugins are managed by the
package.json file. If your plugin information is defined in the
config.xml file, you will need to import the plugins again into Monaca. Please refer to Importing Cordova plugins.
The store-version Monaca Debugger (found in Google play or AppStore) only includes the core Cordova plugins. If your project contains any third party Cordova plugins besides the core Cordova plugins, you will need to build a custom debugger to test it. A custom debugger will only include the plugins used in the project. Please refer to:
For the Monaca CLI, you can open the GUI page by running
monaca remote config in the project directory.
For the Monaca Localkit, you can go there by clicking the
Please note that the
loader.js file loads also the
cordova.js file. Therefore, if you are going to include the above lines, you can remove this line:
Lastly, please notice the following points since they are important when working with the Monaca Debugger and the Monaca Build Server.
The output folder for the building process must be
www. You may need to change the build output to
Make sure that opening the
index.html file over
file:// works. For example, you may need to set
<base href="./" in the