WARNING: Tried to load angular more than once.

[umairch]

Dear @lirantal ,
I just want to ask you two questions.
1- we are going to port one of our ERP solution from 0.4.2 to 0.5.0 MEAN.JS version is it the wise choice and is it stable enough to port an SAAS level Application ?
2- For trial Purpose we have started porting according to MEAN.JS 0.5.0 standards we are going all good and implemented major changes, USER module and core module according 0.5.0 standard and also implemented some modules according 0.5.0 standard but randomly in some modules when we go from one state to another or refresh page and then go to some other state, we are getting error, "Tried to load angular more than once". I figured out it is happening due to Jquery when i comment out Jquery from my project all things work fine. The Question is, Jquery is dependency? , if yes then which version is suitable to use with MEAN.JS version 0.5.0
your quick response will be highly appreciated 😃

[umairch]

@mleanos
@simison

[PierreBrisorgueil]

hello, already have apps based on 0.5 in production without problems :)
for your problem are you sure your try the last release ? node version ?

[umairsch]

using this release
https://github.com/meanjs/mean/releases/tag/0.5.0
node version is not an issue right now getting error at angular side. I am trying to porting a solution 0.4.2 to 0.5.0, have done all necessary things but this error randomly occurred.

[PierreBrisorgueil]

ok, I didn't say the node version was an issue, i just wanted to know it to have the same conf for try.
On my side, node v7.10 - bower 1.8 - npm 5.2

npm install
bower install

everything is fine with this download : https://github.com/meanjs/mean/releases/tag/0.5.0

jQuery is not a dependency.
Include Last Jquery with "bower install jquery --save" => jQuery v3.3.1
call this in /config/assets files 'public/lib/jquery/dist/jquery.min.js'
and everything is ok for me

can you follow this process, after clean your bower & npm dependencies and on a clean download of 0.5.0 ?

if it's ok, compare files between 0.4.2 and 0.5.0 and check if already is really done. Seems to be something with template change or things like this.

I do not know why but I had this error also during a migration. It was a mistake on this migration, I'll tell you if it's up to me. The alternative is to initialize a new clean project and add your modules to it.