Thanks
I think I solve this issue anyway by myself.
It turns out that there is a name conflict of that you expect from the ionic pro system when building and when you build a package on your local system.
The solutions was more simple doing this:
In the package.json file I have now:
"scripts": {
"build": "ionic-app-scripts build",
....
But I change that to
"scripts": {
"build:local": "ionic-app-scripts build",
"build": "true",
Or the name “build:local” could be customized as you like it. But it is important that you keep “build” as “true” according to the website : Failed-build-on-Ionic-1-app-Missing-build-script if you
wanna integrate your code and build system on your system with the ionic pro system.
Don’t ask me why , but it looks like there could be a name conflict here or some kind of a miss configuration that “ionic pro” system has. But not sure.
This now works on my system which was the above configuration I showed.
Note:
I now also not having any issue with the “module provider couldn’t be found” which was one issue that followed when using the ionic-app-scripts 2.5.3 or 3.0.0 to “build”.
But I think this is more a issue on ionic pro rather in the app script.