Ioinic updated, serve fail, Gulpfile.js can't be found

It prompted you to upgrade and install some stuff, didn’t it?
If not, did you really run ionic serve in the correct folder?

OK, i m close to the point where I think i hv to give up…

after comparing the files I think there are a lot of breaking changes. The file structure was completely different.

I think I hv to trace back the change logs from all the way back… and it’s a lot of changes, some part of the file are now supposed to be separated, and the hierarchy was different.

Is there a smarter way of doing it? or the only way is to follow each of the version change logs step by step?

what annoys me is that the original project cant be fired up. If I go through the change log on each version one by one, steps by step, how do i guarantee the ionic compiler and all the npm dependencies are running on the exact version?

What’s your take on this? Do u think it’s come to a point where rebuilding the whole thing to the latest ionic version would be a more easier approach?.. of cuz i would hv to spend time learning the new way of things…

I don’t think you are far from getting it running, but confusing stuff now. The last ionic info you posted again had Ionic Framework 2.3.0 which shouldn’t be the if you had run the command in the directory of your old state of the app. Take a deep breath and start here again and do what I wrote there: Ioinic updated, serve fail, Gulpfile.js can’t be found

This is probably a fairly minor issue, but I’m concerned about @angular/router. I’m under the impression that it is not compatible with Ionic.

So I woke up this morning and decided to the take a deep breathe and try that again.

I reaslize I hv to do a ionic uninstall -g and a sudo npm install -g ionic@2.0.0-beta.10 right?

It threw me with some errors:

Error: Cannot find module 'gauge'
    at Function.Module._resolveFilename (module.js:485:15)
    at Function.Module._load (module.js:437:25)
    at Module.require (module.js:513:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/ionic/node_modules/ionic-app-lib/node_modules/node-sass/node_modules/node-gyp/node_modules/npmlog/log.js:3:13)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
Build failed
npm WARN fsevents@1.0.5 had bundled packages that do not match the required version(s). They have been replaced with non-bundled versions.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.5 (node_modules/ionic/node_modules/ionic-app-lib/node_modules/webpack/node_modules/watchpack/node_modules/chokidar/node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.0.5 install: `node-pre-gyp install --fallback-to-build`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@3.4.2 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the node-sass@3.4.2 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

I tried installing globally the fsevets@1.0.5 and node-sass@3.4.2 as promoted, but it doesnt seem to solve anything. ionic@2.0.0-beta.10 just wont install on my machine.

I guess I m now facing the problem of how to downgrade and install ionic…?
I dont come from a programming background so this is really a learning curve for me.

No. Ionic Framework is not Ionic CLI.

You need the most current Ionic CLI. When you do npm install in the project directory, you install the ionic-angular (Ionic Framework) version that is defined in package.json You will see this in ionic info when you run it in the project directory.

(Please uninstall ionic and reinstall the current version again)

Bear with me @Sujan12 , reasons i thought i hv to uninstall ionic cli is that, I delete the project node module folder to do a local npm install a couple of times, but ionic info still shows me using the 2.3.0 version.

So logically, I thought, Oh, maybe I hv to roll back the CLI globally…

That said, now I hv the npm install -g ionic@latest installed again, with no problem there.
Then I do a fresh local npm install in the project folder with the package.json, just to be sure, i post it here again:

{
  "dependencies": {
    "@angular/animations": "^4.2.3",
    "@angular/common": "2.0.0-rc.3",
    "@angular/compiler": "2.0.0-rc.3",
    "@angular/compiler-cli": "^2.4.8",
    "@angular/core": "2.0.0-rc.3",
    "@angular/forms": "^4.2.3",
    "@angular/http": "2.0.0-rc.3",
    "@angular/platform-browser": "2.0.0-rc.3",
    "@angular/platform-browser-dynamic": "2.0.0-rc.3",
    "@angular/platform-server": "^4.2.3",
    "@angular/router": "^2.0.0-rc.2",
    "@angular/tsc-wrapped": "^4.2.3",
    "@ionic/app-scripts": "^1.3.7",
    "autoprefixer": "^7.1.1",
    "es6-shim": "^0.35.0",
    "ionic-angular": "2.0.0-beta.10",
    "ionic-native": "1.3.2",
    "ionicons": "3.0.0",
    "ng2-simple-page-scroll": "^1.0.2",
    "node-pre-gyp": "^0.6.36",
    "reflect-metadata": "^0.1.3",
    "rxjs": "5.0.0-beta.6",
    "sw-toolbox": "^3.6.0",
    "typescript": "^2.3.4",
    "zone.js": "^0.6.12"
  },
  "devDependencies": {
    "@ionic/app-scripts": "0.0.47",
    "typescript": "2.0.9"
  },
  "cordovaPlugins": [
    "cordova-plugin-device",
    "cordova-plugin-console",
    "cordova-plugin-whitelist",
    "cordova-plugin-splashscreen",
    "cordova-plugin-statusbar",
    "ionic-plugin-keyboard"
  ],
  "cordovaPlatforms": [
    "ios",
    {
      "platform": "ios",
      "version": "",
      "locator": "ios"
    }
  ],
  "name": "cow",
  "description": "cow: An Ionic project",
  "scripts": {
    "clean": "ionic-app-scripts clean",
    "build": "ionic-app-scripts build",
    "lint": "ionic-app-scripts lint",
    "ionic:build": "ionic-app-scripts build",
    "ionic:serve": "ionic-app-scripts serve"
  }
}

When I run ionic info:

[ERROR] Error with ./node_modules/ionic-angular/package.json file:
        FILE_NOT_FOUND

global packages:

    @ionic/cli-plugin-proxy : 1.3.1
    @ionic/cli-utils        : 1.4.0
    Gulp CLI                : CLI version 3.9.1 Local version 3.9.1
    Ionic CLI               : 3.4.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-gulp          : 1.0.1
    @ionic/cli-plugin-ionic-angular : 1.3.1
    Ionic Framework                 : not installed

System:

    Node       : v8.0.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.3 Build version 8E3004b 
    ios-deploy : 1.8.6 
    ios-sim    : 5.0.8 
    npm        : 5.0.3 

err… it says ’ Ionic Framework : not installed’,… this is new to me, not knowing how this could happen.

Nevertheless I try to run ionic serve, it brought me back to the original topic of this post…
Gulpfile issue reemerges:

[ERROR] Gulpfile not found: ./gulpfile.js
        You can set the gulpFile attribute in ionic.config.json for custom
        Gulpfile locations, otherwise the default Ionic Gulpfile can be
        downloaded from
        https://github.com/ionic-team/ionic-app-base/blob/master/gulpfile.js
        
        Or, if you no longer use gulp, you can remove the CLI Gulp Plugin:
        
        npm uninstall --save-dev --save-exact @ionic/cli-plugin-gulp@latest

at this point, I hv the gulpfile.js file removed, and edited the package.json as you wrote.
felt like i am walking in circles again :sob:

Fascinatingly @angular/router really got removed in beta10: https://github.com/ionic-team/ionic2-app-base/commit/493c074a1fae51d2d8fe78b329bf8d824f8434d4#diff-b9cfc7f2cdf78a7f4b91a753d10865a2L9
(So it was there before, but shouldn’t be there any more in this project anyway)

Update: Ahh, the upgrade instructions were wrong and included the router: https://github.com/ionic-team/ionic/blob/master/CHANGELOG.md#steps-to-upgrade-to-beta-10

That is very strange and shouldn’t be the case.[quote=“ultradryan, post:27, topic:94748”]
err… it says ’ Ionic Framework : not installed’,… this is new to me, not knowing how this could happen.
[/quote]

Something is broken. Somehow, somewhere…