1

I've been trying to upgrade medium sized project from Angular version 1.2.16 to 1.6.4. The problem here is, I can't jump from one version to another, so I have to use both versions at the same time in the project. However, I couldn't able to find a well prepared guide to follow. There are some different steps which is described in SO or in Github pages. But anyhow, I couldn't manage it.

Here are some SO links that I've been reading during this time.

1 - Multiple versions of AngularJS in one page

2 - Supporting Multiple Versions of AngularJS

3 - https://github.com/angular-translate/angular-translate/wiki/How-to-use-a-different-version-of-AngularJS-using-Bower

And below is my bower.json:

{
  "name": "takademi",
  "version": "0.0.0",
  "dependencies": {
    "angular": "1.2.16",
    "json3": "~3.3.1",
    "es5-shim": "~3.1.0",
    "angular-cookies": "1.2.16",
    "angular-sanitize": "1.2.16",
    "angular-animate": "1.2.16",
    "angular-route": "1.2.16",
    "angular-bindonce": "~0.3.1",
    "restangular": "~1.4.0",
    "angular-base64": "~2.0.2",
    "lodash": "~2.4.1"
  },
  "devDependencies": {
    "angular-mocks": "1.2.16",
    "angular-scenario": "1.2.16"
  },
  "appPath": "app"
}

Can you suggest any good guide, blog, video tutorial for me to follow?

Thanks in advance.

7
  • Okay, then any good idea? @Phil Commented Jun 21, 2017 at 6:17
  • this is a truly terrible idea. just upgrade to the latest version man. Commented Jun 21, 2017 at 6:34
  • Why can't you "jump from one version to another"? If your aim is to migrate your apps from AngularJS 1.2 to 1.6, why are you attempting to run multiple versions instead of performing the upgrade? Commented Jun 21, 2017 at 6:34
  • There is no fullproof solution to this. Try to narrow down your problem by posting the errors you're facing, and may someone be able to help you then. Commented Jun 21, 2017 at 6:35
  • I can't jump from 1.2 to 1.6, because it is a medium sized project which is very close to be a big sized one. And I am the only person who is going to handle with this project. So I have to deploy at least some parts of it piece by piece to let others not affected. Because there is such a huge risk if I upgrade from 1.2 to 1.6 in one step, it will take so long, and there will be hell to solve bugs on my own (tons of customers are using the project). So running multiple versions is the answer for me here. Commented Jun 21, 2017 at 6:43

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.