Unable to run project after migration from ionic v2 to ionic v3


#1

Hello,

I face some issue after the migration of project to ionic v3. In fact I followed the tutorial below to carry out the migration.

After I run my project ionic serve --lab but it doesn’t work, I have this error

I have this message, yet the package exists in the node_module directory

And in the console of my browser I can see that there is apparently a worry with an abstract class. Here is the code of the abstract class in question.

import {Injectable} from "@angular/core";
import {GlobalsConstants} from "../constants/globals.constants";
import {NavController, NavParams} from "ionic-angular";

@Injectable()
export abstract class AbstractLoggedPage {
  
  protected logged: boolean;
  protected loggedUser;
  protected nav;
  protected navParams;
  
  
  constructor(navCtrl?: NavController, navParams?: NavParams) {
    this.nav = navCtrl;
    this.navParams = navParams;
    this.loggedUser = JSON.parse(localStorage.getItem(GlobalsConstants.USER_LOGGED));
  }
  
  static checkLogin(): boolean {
    return !!localStorage.getItem("logged");
  }
  
  ionViewCanEnter(): boolean{
    if(AbstractLoggedPage.checkLogin()){
      this.initData();
      return true;
    } else {
      return false;
    }
  }
  
  abstract initData();
  
}

Can anyone help me understand what is wrong ?


#2

Same issue i faced. Solved it using the command in the following link
Ionic CLI v3 Beta


#3

What is your ionic info output and package.json content?


#4

ionic info

global packages:

    @ionic/cli-utils : 1.4.0
    Ionic CLI        : 3.4.0

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-ionic-angular : 1.3.1
    Ionic Framework                 : ionic-angular 3.4.2

System:

    Node       : v7.8.0
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.3 Build version 8E3004b 
    ios-deploy : 1.9.1 
    ios-sim    : not installed
    npm        : 4.2.0 

Package.json


#5

What command exactly ?


#6

#7

Have you tried deleting node_modules and running npm install?


#8

Yes I did it but it did not change much, the error persists


#9

Do you somewhere import this module in your code?
Does it actually exist in node_modules?