@rgins16 Opera and Chrome use the same engine so there shouldn’t be problems. About IE I’m not so sure, probably there are components like ons-range that do not work well due to technology/CSS limitations in IE. We can try to fix bugs reported but it is not a priority (of course, PRs are welcome).
@Fran-Diox No it’s not like that. I see that Monaca have strong structure of the projects’f folders and files and Monaca have some expectations from imported Cordova projects.
For example content of Meteor .meteor\local\cordova-build\ folder doesn’t have index.html file in \www\ subfolder ( this file stored in \www\application\ subfolder). Also in Meteor’s Cordova project resources files (icons and splashscreens) stored in resources folder instead Monaca’s res folder.
So, when you import this project to the Monaca you see stub index.html generated by Monaca in www folder, you see new res folder with standard Monaca icons and splashscreens, also <content src=""/> in the config.xml replaced from Meteor’s entry point to newly generated \www\index.html, and some other strange things