We upgraded our app from Angular 6 to 7. After the upgrade, we are getting a bunch of errors with the Resize Sensor when building in production mode. I attached a screenshot of the error. For troubleshooting, I created a brand new angular 7 app, added the dropdowns package along with popup and resize sensor packages, and get similar errors. Build is fine in dev mode.
3 Answers, 1 is accepted
0
Jacky
Top achievements
Rank 1
Rank 1
answered on 23 Apr 2019, 08:23 PM
I was able to resolve this in our app and test app by just deleting the package-lock.json and then regenerating it. Not sure why that would cause issues with a brand new angular app? Shouldn't the ng add commands update the package-lock.json correctly?
0
Hello Jacky,
The package-lock.json file is created the first time npm install is run and the packages, specified in the package.json file are installed. From then on it keeps the exact original versions that were installed the first time, and even new versions are specified in the package.json file, the one existing in the package-lock.json file are not updated until this file is remove, and recreated (by running npm install anew).
This is why we are always recommending the package-lock.json file and even the node_modules folder when updating our (and other) packages to make sure that the latest versions of all packages and their dependencies are actually installed. Sometimes cleaning the npm cache is also necessary.
Regards,
Dimiter Topalov
Progress Telerik
The package-lock.json file is created the first time npm install is run and the packages, specified in the package.json file are installed. From then on it keeps the exact original versions that were installed the first time, and even new versions are specified in the package.json file, the one existing in the package-lock.json file are not updated until this file is remove, and recreated (by running npm install anew).
This is why we are always recommending the package-lock.json file and even the node_modules folder when updating our (and other) packages to make sure that the latest versions of all packages and their dependencies are actually installed. Sometimes cleaning the npm cache is also necessary.
Regards,
Dimiter Topalov
Progress Telerik
Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
0
Jacky
Top achievements
Rank 1
Rank 1
answered on 24 Apr 2019, 07:28 PM
Thanks for the explanation! I deleted the node_modules folder and ran npm install a bunch of times. Now I will add deleting package-lock.json to my workflow when I do a major upgrade.