Closed deepaksm1 closed 9 years ago
I just updated with the latest fayde, my build is fine. But I have seen build errors often when update to a new version, I think most of them are due the dependencies are still in older version. Not sure if it is a problem of bower update, or a cache problem, or because bower.json not updated in the Fayde's project to require the latest dependencies.
For example, the latest minerva is v. 0.4.23, the latest perfex is v. 0.1.14, but here is what listed in fayde's bower.json: "minerva": "~0.4.22", "perfex": "~0.1.0".
Try running grunt lib:reset
if this ever happens.
Yes, that's what I usually do. But sometimes, that doesn't work either.
I have all the Fayde projects cloned, and I'm mainly working on the Fayde.Controls project most of time. When you have a new build on fayde/nullstone/minerva, I usually just update my bower.json under Fayde.Controls project to point to the new version. After bower update, sometime I can see build error, And I can tell the build error was due to dependency mismatch. This can be very frustrating, has wasted a lot of time in development.
Fayde does not need to list the latest minerva or nullstone versions. The tilde at the beginning allows bower to resolve any "compatible" version. In other words, when installing dependencies ~0.4.22 will install 0.4.23 because it is the latest compatible version. It will not install 0.5+.
I am creating new fayde project using yo fayde. grunt lib:reset
task is not there.
My issue is solved.
Updated new fayde version its giving me below errors