@ihadeed yea, but I think ionic documentation changed, now I found this in docu
“Ionic 2 applications are created as TypeScript by default” … “Want to use JavaScript instead? Pass the --no-ts flag and get a project set up for JavaScript instead.”
So I think the behavior changed, but it doesn’t work? Or what’s happened?
hm? I think it’s not right what @zhangpeimingsays, the cli always has js as default. But now the documentation writes typescript is the standard but the cli continues to use js as standard. So I think the documentation is misleading now or the documentation changed but the new cli standard is not released yet?
I’m pretty sure the document changed, so before in the documentation was described we have to set --ts for typescript. And now the documentation write --ts is set by default but the cli works still with js as default.
You’re right. Looking at the following commit it seems that the documentation was updated although the CLI still doesn’t work this way. Judging by the following open issue the transition to TypeScript as default is still a work in progress:
All new v2 projects started will be TypeScript. We have removed the option to generate new projects using JavaScript. I have removed any reference to the --js, --no-ts, or --ts flags because they are no longer relevant.
So let’s go back using Ionic v1, guys
And let’s hope they do not delete it… They have a very strange attitude… No compatibility is like going back to '90