Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Upgrading 1.3.4 to 1.5.0 doesn't update package.json

See original GitHub issue

Hey Guys, First off, great work on the CLI, and the project upgrade stuff! So I was trying to upgrade my samples (js-skype-status, react-skype-status) from 1.3.4 to 1.5.0 and I was instructed to run the following commands

npm update @microsoft/sp-core-library@1.5.0
npm update @microsoft/sp-lodash-subset@1.5.0
npm update @microsoft/sp-office-ui-fabric-core@1.5.0
npm update @microsoft/sp-webpart-base@1.5.0
npm update @types/webpack-env@1.13.1
npm i @types/es6-promise@0.0.33
npm update @microsoft/sp-build-web@1.5.0
npm update @microsoft/sp-module-interfaces@1.5.0
npm update @microsoft/sp-webpart-workbench@1.5.0
npm update @types/chai@3.4.34
npm update @types/mocha@2.2.38
npm update react@15.6.2
npm update react-dom@15.6.2
npm update @types/react@15.6.6
npm update @types/react-dom@15.5.6
npm uninstall @types/react-addons-shallow-compare
npm uninstall @types/react-addons-update
npm uninstall @types/react-addons-test-utils

The issue with that is it doesn’t save to the package.json for the update commands.

npm i @microsoft/sp-core-library@1.5.0 -S --save-exact
npm i @microsoft/sp-lodash-subset@1.5.0 -S --save-exact
npm i @microsoft/sp-office-ui-fabric-core@1.5.0 -S --save-exact
npm i @microsoft/sp-webpart-base@1.5.0 -S --save-exact
npm i @types/webpack-env@1.13.1 -S --save-exact
npm i @types/es6-promise@0.0.33
npm i @microsoft/sp-build-web@1.5.0 -D --save-exact
npm i @microsoft/sp-module-interfaces@1.5.0 -D --save-exact
npm i @microsoft/sp-webpart-workbench@1.5.0 -D --save-exact
npm i @types/chai@3.4.34 -D --save-exact
npm i @types/mocha@2.2.38 -D --save-exact
npm i react@15.6.2 -S --save-exact
npm i react-dom@15.6.2 -S --save-exact
npm i @types/react@15.6.6 -S --save-exact
npm i @types/react-dom@15.5.6 -S --save-exact
npm uninstall @types/react-addons-shallow-compare -S
npm uninstall @types/react-addons-update -S
npm uninstall @types/react-addons-test-utils -S

Instead does the trick node: 10.3.0 npm: 6.1.0

Issue Analytics

State:
Created 5 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

andrewconnellcommented, Jun 26, 2018

Update only respects symver… in this case install should be used.

0reactions

baywetcommented, Jun 26, 2018

yeah, in this case ~ was specified before 1.3.4 FYI https://github.com/SharePoint/sp-dev-fx-webparts/pull/545/files#diff-c2fdb5502e5ed6e580d5e7cb08778c80

Top Results From Across the Web

Upgrading 1.3.4 to 1.5.0 doesn't update package.json #501

Hey Guys, First off, great work on the CLI, and the project upgrade stuff! So I was trying to upgrade my samples (js-skype-status, ......

npm update does not do anything - Stack Overflow

When I execute this code in my application folder where the package. json is located: npm update or npm update --save-dev it does...

Upgrade Pandas Version to Latest or Specific Version

If you are using pip, you can upgrade Pandas to the latest version by issuing the below command. If you are not aware,...

package.json - npm Docs

Description. This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just...

npm/CHANGELOG.md - UNPKG

27, updating a couple of dependencies that were preventing `npmlog` from ... 2131, [#8197](https://github.com/npm/npm/issues/8197) `init-package-json@1.5.0`.